The AFX Server is in a
Running state but all previously working RSA Identity Governance & Lifecycle AFX Connectors are stuck in a
Deployed state and do not progress to a
Running state. For example,
Symptoms include:
- The $AFX_HOME/esb/logs/esb.AFX-MAIN.log file has the following errors:
2015-11-20 00:05:55.331 [ERROR] com.aveksa.afx.server.manager.MMCRequestManagerImpl:84 - Server Id setup try count exceeded
2015-11-20 00:05:55.331 [ERROR] com.aveksa.afx.server.manager.MMCRequestManagerImpl:85 - Please verify that the MMC console is running and Host & Port in the URL are correct.
2015-11-20 00:05:55.332 [ERROR] com.aveksa.afx.server.manager.MMCRequestManagerImpl:64 - Unable to initialize the MMC Request Manager
com.aveksa.afx.server.manager.MMCException: Unable to retrieve and setup the Afx server Id information
....
2015-11-20 00:05:55.692 [ERROR] com.aveksa.afx.server.manager.MMCRequestManagerImpl:118 - Unable to get status for all Connectors from MMC
com.aveksa.afx.server.manager.MMCException: Failed to get flows for server. No associated server Id. Check Request Manager Initialization
- A restart of AFX, RSA Identity Governance & Lifecycle, and even a system reboot does not fix the problem.
- acm status indicates that ActiveMQ is not running.