000034649 - RSA Identity Governance and Lifecycle on-premise Access Fulfillment Express (AFX) server is in Running state but AFX connectors remain in Deployed state

Document created by RSA Customer Support Employee on Jan 13, 2017Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000034649
Applies ToRSA Product Set: RSA Identity Governance and Lifecycle
RSA Product/Service Type: All
RSA Version/Condition: 6.9.1+
Platform: Linux
Environment: MyAccessLive
Product Description: Access Fulfillment  Express
IssueFor MyAccessLive environment, the on-premise Access Fulfillment Express (AFX) server is running, but the AFX Connectors stay in a DEPLOYED state.
The on-premise AFX is using Java version 1.6. The following commands are run to make sure the variables of $JAVA_HOME and $PATH are both set up and point to the path correctly:
afxusr@rsa2:~> echo $JAVA_HOME
afxusr@rsa2:~> echo $PATH

After running the commands, the following errors have been found in the log files.
  1. Run the following command to check the status of the AFX server.  Note that the mmc-console will show as not running.
afx_server status
mmc-console is not running

  1. Navigate to the $AFX/mmc-console/logs directory.  It will contain only the catalina.out, which has one line, details as below:
/home/afxusr/AFX/mmc-console/bin/catalina.sh: line 389: /usr/java/jre1.6.0_45/bin/bin/java: No such file or directory

  1. The $AFX_HOME/AFX/mule/logs/ mule.AFX-MAIN.log contains the following errors:
2017-01-05 15:39:19.278 [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
at com.aveksa.afx.server.manager.MMCRequestManagerImpl.getFlowList(MMCRequestManagerImpl.java:168)
at com.aveksa.afx.server.manager.MMCRequestManagerImpl.getAllConnectorStatus(MMCRequestManagerImpl.java:101)
at com.aveksa.afx.server.component.PrimaryRequestConstructorComponent.constructRequest(PrimaryRequestConstructorComponent.java:59)
at sun.reflect.GeneratedMethodAccessor85.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.mule.model.resolvers.AbstractEntryPointResolver.invokeMethod(AbstractEntryPointResolver.java:151)
at org.mule.impl.model.resolvers.AnnotatedEntryPointResolver.invoke(AnnotatedEntryPointResolver.java:141)
at org.mule.model.resolvers.DefaultEntryPointResolverSet.invoke(DefaultEntryPointResolverSet.java:39)
at org.mule.component.DefaultComponentLifecycleAdapter.invoke(DefaultComponentLifecycleAdapter.java:343)
at org.mule.component.AbstractJavaComponent.invokeComponentInstance(AbstractJavaComponent.java:86)
at org.mule.component.AbstractJavaComponent.doInvoke(AbstractJavaComponent.java:77)
at org.mule.component.AbstractComponent.invokeInternal(AbstractComponent.java:126)
at org.mule.component.AbstractComponent.access$000(AbstractComponent.java:6
at org.mule.component.AbstractComponent$1$1.process(AbstractComponent.java:242)
at org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor.execute(ExceptionToMessagingExceptionExecutionInterceptor.java:27)
at org.mule.execution.MessageProcessorNotificationExecutionInterceptor.execute(MessageProcessorNotificationExecutionInterceptor.java:46)

CauseThe $JRE_HOME variable is not defined correctly.

Tomcat uses the value of $JRE_HOME if it is set; otherwise it sets the $JRE_HOME variable to the value of the $JAVA_HOME variable. For some reason the  $JRE_HOME variable is set to /usr/java/jre1.6.0_45/bin instead of /usr/java/jre1.6.0_45.

ResolutionThe way to fix this is to set the value of the $JRE_HOME variable to be the same as the value of $JAVA_HOME variable.
  1. To verify, execute the following commands as the afx user:
afxusr@rsa2:~> echo $JAVA_HOME
afxusr@rsa2:~> echo $JRE_HOME

  1. If the values returned are undefined, are pointing to any version other than Java 1.6 JDK or to another directory, set the variable of $JRE_HOME to be the same as the $JAVA_HOME variable, using one of the commands below:
afxusr@rsa2:~> export JRE_HOME=$JAVA_HOME


afxusr@rsa2:~> export JRE_HOME=/usr/java/jre1.6.0_45

  1. Then restart the on-premise AFX Server. The issue can be resolve. The AFX Connectors should show in a Running state.