000037477 - Access Fulfilment Express (AFX) is unresponsive even though the AFX server and most connectors are running in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Jun 5, 2019
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000037477
Applies ToRSA Product Set: Identity Governance & Lifecycle
RSA Version/Condition: 7.1.0
 
IssueRSA Identity Governance & Lifecycle Access Fulfillment Express (AFX) is unresponsive even though the AFX server status shows it is Running and most connectors show with a status of Running.

The Connectors page may show one or more connectors with a status of Not Deployed (Missing required settings), yet the current version of the AFX templates have been imported.

The aveksaServer.log shows the following INFO level log messages over and over again with events occurring every few minutes:
 
05/09/2019 22:42:06.764 INFO (default task-368) [com.aveksa.afx.server.service.handler.AFXPrimaryRequestHandler] Sending connector Test1 to AFX to be deployed (database revision 3, database create date Tue Feb 26 13:04:39 CST 2019, current AFX revision null, current AFX create date null) 05/09/2019 22:42:06.764 INFO (default task-368) [com.aveksa.afx.server.service.handler.AFXPrimaryRequestHandler] Loading 1 connector(s) to deploy 05/09/2019 22:42:07.500 INFO (default task-368) [com.aveksa.afx.server.service.handler.AFXPrimaryRequestHandler] Loaded 1 connector(s) to deploy 05/09/2019 22:42:07.501 INFO (default task-368) [com.aveksa.afx.server.service.handler.AFXPrimaryRequestHandler] Loading transport(s) for the 1 connector(s) to deploy 05/09/2019 22:42:07.517 INFO (default task-368) [com.aveksa.afx.server.service.handler.AFXPrimaryRequestHandler] Loaded 1 transport(s) 05/09/2019 22:42:07.517 INFO (default task-368) [com.aveksa.afx.server.service.handler.AFXPrimaryRequestHandler] Loading files for the 1 transport(s) and 1 connector(s) to deploy 05/09/2019 22:42:07.518 INFO (default task-368) [com.aveksa.afx.server.service.handler.AFXPrimaryRequestHandler] Loaded 11 file(s)
CauseThe problem here is the one or more connectors in a Not Deployed state and missing required settings. This may occur if something interrupts the deployment or saving of the details for a Connector. The Connector is left in an indeterminate state that prevents it from being deployed correctly. The failing redeployment of the connector over and over again may cause the AFX server to become unresponsive. 

 
ResolutionAt this time there is no resolution to this issue. The cause of this problem has not been identified. 
Workaround
  • Edit the Connectors listed in the INFO level log message and attempt to supply the missing information that is preventing them from being deployed. 
  • Alternatively delete the problem Connector and create it again.
  • Restart AFX after these steps have been completed. 
Notes

The Connector cannot be deployed if any of the required fields in the connector are missing.   



It is not possible to save a connector without supplying a value for all required fields but there are some situations where an imported connector may not have values for all required fields.

Attachments

    Outcomes