Unable to create or Edit Agent on Applications Manager version 9.3.4

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

After upgrading to Applications Manager version 9.3.4, the creation of a new Agent no longer functions. This can be reproduced with the following steps:

1. Open up Agent Selector menu
2. Select New
3. Enter in required values (Name, OS Type, Description, Output Directory, AgentService IP, User, Sleep Time, CPU Limit, Thread Schedule)
4. Select Apply or Okay

Nothing happens and no error is received. However, in the client logs, the following error is seen:

Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
 at com.appworx.client.screen.agentmgr.AgentMgr.ɨAgentMgr.java:445)
 at com.appworx.client.screen.admin.D$_A$1.run(TabbedDialog.java:622)
 at java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313)
 at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:770)
 at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
 at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)
 at java.base/java.security.AccessController.doPrivileged(Native Method)
 at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
 at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:740)
 at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
 at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
 at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
 at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
 at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
 at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)

 

Environment

Release : 9.3.4

Component : APPLICATIONS MANAGER

Cause

This is a bug related to a change made in 9.3.4

Resolution

This behavior is fixed in Applications Manager version 9.3.5.

*Workaround*

Use Applications Manager Client version 9.3.3HF1 or 9.3.5 with following added in client.properties file:

runOptions=-Xmx256m -Dappworx.development=true

Attached to the article is the 9.3.3HF1 client.zip