000038161 - AFX new or updated Connectors remain in a Deployed state and the MMC application fails to load in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Nov 20, 2019Last modified by RSA Customer Support Employee on Nov 21, 2019
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000038161
Applies ToRSA Product Set: Identity Governance & Lifecycle
RSA Version/Condition: 7.1.0, 7.1.1
 
IssueNew or updated AFX connectors remain in a Deployed state. Existing connectors may continue to be in a Running state.
 
User-added image


Additional Symptoms are:



  • The AFX Server shows as Running in the user interface (AFX > Servers).
  • The afx status command shows that AFX is running.
  • The Mule Management Console (MMC) fails to load.
  • The $AFX_HOME/mmc-console/logs/catalina.out shows a SEVERE error indicating that MMC has failed to deploy and that the details are in the container log file.


Oct 28, 2019 4:51:13 PM org.apache.catalina.core.StandardContext startInternal
SEVERE: One or more listeners failed to start. Full details will be found in the appropriate container log file


  • The catalina container log file $AFX_HOME/mmc-console/logs/localhost.YYYY-MM-DD.log shows a SEVERE exception referencing:

java.lang.NoSuchFieldError



Oct 28, 2019 4:51:13 PM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Exception sending context initialized event to listener instance of class
org.springframework.web.context.ContextLoaderListener org.springframework.beans.factory.BeanCreationException:
Error creating bean with name 'galaxyService' defined in class path resource
[META-INF/applicationContext-gwtconsole-galaxy.xml]:
Cannot resolve reference to bean 'serverManager' while setting bean property 'serverManager';
nested exception is org.springframework.beans.factory.BeanCreationException:
Error creating bean with name 'serverManager' defined in class path resource [META-INF/applicationContext.xml]:
Cannot resolve reference to bean 'alertManager' while setting bean property 'alertManager';
nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name
'alertManager' defined in class path resource [META-INF/applicationContext.xml]: Cannot resolve reference
to bean 'v1/alertService' while setting bean property 'alertService'; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'v1/alertService'
defined in class path resource [META-INF/applicationContext-console.xml]: Cannot create inner bean
'com.mulesoft.mmc.remoting.HttpInvokerRequestExecutor#21735e85' of type
[com.mulesoft.mmc.remoting.HttpInvokerRequestExecutor] while setting bean property 'httpInvokerRequestExecutor';
nested exception is org.springframework.beans.factory.BeanCreationException:
Error creating bean with name 'com.mulesoft.mmc.remoting.HttpInvokerRequestExecutor#21735e85'
defined in class path resource [META-INF/applicationContext-console.xml]: Cannot resolve reference to bean
'socketFactory' while setting bean property 'socketFactory'; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'tlsConfiguration'
defined in class path resource [META-INF/applicationContext-console.xml]: Cannot resolve reference to bean
'keyService' while setting constructor argument; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'keyService'
defined in class path resource [META-INF/applicationContext-console.xml]: Invocation of init method failed;
nested exception is java.lang.NoSuchFieldError: AuthorityKeyIdentifier


  • The $AFX_HOME/esb/logs/esb.AFX-MAIN.log shows that AFX is unable to contact the MMC application.


2019-10-28 19:23:43.760 [ERROR] com.aveksa.afx.server.manager.MMCRequestManagerImpl:136 -
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


 
CauseThis issue may occur if there is a java class file conflict in the SSL libraries for the MMC application. The most common cause for this issue is a class file conflict with the third party BouncyCastle crypto library embedded in the AFX application and located in $AFX_HOME/esb/lib/opt/bcprov-jdk16-1.46.jar. This is a known issue with the Access Fulfillment Express (AFX) MMC application which is not compatible with newer versions of this library. 

Note that this issue is characterized by the specific error, java.lang.NoSuchFieldErrorin the $AFX_HOME/mmc-console/logs/localhost.YYYY-MM-DD.log file. The other AFX error messages may be common to other AFX failure modes.



 
ResolutionEnsure that the main java classpath (/usr/lib64/jvm/java-1.8.0-openjdk-1.8.0/jre/lib/ext/) does not include the third party BouncyCastle crypto library.

 

Attachments

    Outcomes