000037477 - AFX is unresponsive and one or more AFX Connectors are in a Not Deployed state in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Jun 5, 2019Last modified by RSA Customer Support Employee on Apr 7, 2020
Version 4Show Document
  • View in full screen mode

Article Content

Article Number000037477
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.1.0, 7.1.1, 7.2.0
IssueAFX is unresponsive yet the AFX Server status (AFX > Servers) shows as Running.

Most AFX connectors (AFX > Connectors) show as Running but one or more connectors have a status of Not Deployed (Missing required settings). The current version of the AFX templates have been imported.

The aveksaServer.log file ($AVEKSA_HOME/wildfly/standalone/log/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)

Please refer to RSA Knowledge Base Article 000030327 -- Artifacts to gather in RSA Identity Governance & Lifecycle to find the location of the aveksaServer.log file for your specific deployment if you are on a WildFly cluster or a non-WildFly platform. The aveksaServer.log may also be downloaded from the RSA Identity Governance & Lifecycle user interface (Admin > System > Server Nodes tab > under Logs.)
CauseThe problem is that one or more connectors are in a Not Deployed state and missing required settings.

A connector cannot be deployed if any of the required fields in the connector are missing. 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. 
ResolutionTo resolve this issue the missing required settings must be supplied. Follow the steps below.
  1. Edit the connectors listed in the INFO level log message and attempt to supply the missing information that is preventing them from being deployed. 
  2. Alternatively delete the problem connector(s).
  3. Recreate the connector if it is still needed.
  4. Restart AFX after these steps have been completed. Log in as the afx user:

afx stop
afx start