000031862 - RSA Via Lifecycle and Governance Access Fulfillment Express (AFX) Connectors are in a deployed state when they have been working previously

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 5Show Document
  • View in full screen mode

Article Content

Article Number000031862
Applies ToRSA Product Set: RSA Via Lifecycle and Governance 
RSA Product/Service Type: Appliance
RSA Version/Condition: 6.9.1
Platform: Linux
IssueAll AFX Connectors have been working properly, but they are currently in the Deployed state after observing ActiveMQ not running.  Also seeing the current issue after restarting AFX. See the screenshot below.
User-added image
The error message below can be found in the AFX-MAIN.log file.
 

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 
at com.aveksa.afx.server.manager.MMCRequestManagerImpl.initServerId(MMCRequestManagerImpl.java:86) 
at com.aveksa.afx.server.manager.MMCRequestManagerImpl.init(MMCRequestManagerImpl.java:62) 
at com.aveksa.afx.server.component.PrimaryRequestConstructorComponent.init(PrimaryRequestConstructorComponent.java:37) 
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) 
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
at java.lang.reflect.Method.invoke(Method.java:622) 
at org.mule.component.DefaultComponentLifecycleAdapter.initialise(DefaultComponentLifecycleAdapter.java:212) 
at org.mule.component.AbstractJavaComponent.createLifecycleAdaptor(AbstractJavaComponent.java:140) 
at org.mule.component.DefaultJavaComponent.doStart(DefaultJavaComponent.java:71) 
at org.mule.component.AbstractComponent$4.onTransition(AbstractComponent.java:313) 
at org.mule.component.AbstractComponent$4.onTransition(AbstractComponent.java:308) 
at org.mule.lifecycle.AbstractLifecycleManager.invokePhase(AbstractLifecycleManager.java:141) 
at org.mule.component.ComponentLifecycleManager.fireStartPhase(ComponentLifecycleManager.java:71) 
at org.mule.component.AbstractComponent.start(AbstractComponent.java:307) 
at org.mule.processor.chain.AbstractMessageProcessorChain.start(AbstractMessageProcessorChain.java:90) 
at org.mule.construct.AbstractFlowConstruct.startIfStartable(AbstractFlowConstruct.java:326) 
at org.mule.construct.AbstractPipeline.doStart(AbstractPipeline.java:300) 
at org.mule.construct.AbstractFlowConstruct$2.onTransition(AbstractFlowConstruct.java:145) 
at org.mule.construct.AbstractFlowConstruct$2.onTransition(AbstractFlowConstruct.java:141) 
at org.mule.lifecycle.AbstractLifecycleManager.invokePhase(AbstractLifecycleManager.java:141) 
at org.mule.construct.FlowConstructLifecycleManager.fireStartPhase(FlowConstructLifecycleManager.java:95) 
at org.mule.construct.AbstractFlowConstruct.start(AbstractFlowConstruct.java:140) 


2015-11-20 00:05:55.351 [INFO] org.mule.module.client.MuleClient:197 - Using existing MuleContext: org.mule.DefaultMuleContext@52feae2 
2015-11-20 00:05:55.361 [INFO] org.mule.module.client.MuleClient:197 - Using existing MuleContext: org.mule.DefaultMuleContext@52feae2 
2015-11-20 00:05:55.363 [INFO] org.mule.transport.quartz.QuartzConnector:197 - Registering listener: PRIMARY_REQUEST on endpointUri: quartz://primary-request-job 
2015-11-20 00:05:55.363 [INFO] org.mule.lifecycle.AbstractLifecycleManager:197 - Initialising: 'null'. Object is: QuartzMessageReceiver 
2015-11-20 00:05:55.363 [INFO] org.mule.transport.quartz.QuartzMessageReceiver:197 - Connecting clusterizable message receiver 
2015-11-20 00:05:55.364 [INFO] org.mule.lifecycle.AbstractLifecycleManager:197 - Starting: 'null'. Object is: QuartzMessageReceiver 
2015-11-20 00:05:55.368 [INFO] org.mule.transport.quartz.QuartzMessageReceiver:197 - Starting clusterizable message receiver 
2015-11-20 00:05:55.372 [INFO] org.mule.construct.FlowConstructLifecycleManager:197 - Starting flow: AFX_FULFILLMENT_STATE 


2015-11-20 00:05:55.662 [INFO] org.mule.transport.jms.MultiConsumerJmsMessageReceiver:197 - Starting clusterizable message receiver 
2015-11-20 00:05:55.662 [INFO] org.mule.construct.FlowConstructLifecycleManager:197 - Starting flow: AFX_JMS_FULFILLMENT_STATE_RETRY 
2015-11-20 00:05:55.663 [INFO] org.mule.processor.SedaStageLifecycleManager:197 - Starting service: AFX_JMS_FULFILLMENT_STATE_RETRY.stage1 
2015-11-20 00:05:55.665 [INFO] org.mule.transport.jms.activemq.ActiveMQJmsConnector:197 - Registering listener: AFX_JMS_FULFILLMENT_STATE_RETRY on endpointUri: jms://AFX.JMS.FULFILLMENT.STATE.RETRY 
2015-11-20 00:05:55.665 [INFO] org.mule.transport.service.DefaultTransportServiceDescriptor:197 - Loading default inbound transformer: org.mule.transport.jms.transformers.JMSMessageToObject 
2015-11-20 00:05:55.665 [INFO] org.mule.transport.service.DefaultTransportServiceDescriptor:197 - Loading default response transformer: org.mule.transport.jms.transformers.ObjectToJMSMessage 
2015-11-20 00:05:55.666 [INFO] org.mule.lifecycle.AbstractLifecycleManager:197 - Initialising: 'null'. Object is: MultiConsumerJmsMessageReceiver 
2015-11-20 00:05:55.666 [INFO] org.mule.transport.jms.MultiConsumerJmsMessageReceiver:197 - Connecting clusterizable message receiver 
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 
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.NativeMethodAccessorImpl.invoke0(Native Method) 
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
ResolutionThis issue is likely caused by changes that have been made but have not yet been updated.  Therefore, after restarting the AFX server, all the connectors are in a Deployed state.
Follow the steps below to resolve the issue.
  1. Log on to the RSA Via L&G UI.
  2. Go to AFX > Server and select the AFX Server name.
  3. Under the page of the AFX Server name, click on the Download Server Archive button to download the AFXServer.zip file.
User-added image

  1. Copy the AFXServer.zip to the ./home/<afxuser> path on the server.
  2. Run AFX stop.
  3. Rename the original AFX folder to AFX_OLD or other name.
  4. Unzip the AFXServer.zip in the ./home/<afxuser> directory to create a new ./home/<afxuser>/AFX directory.
unzip AFXServer.zip

  1. Set appropriate file permissions:
    cd /home/<afxuser>AFX
    sh bin/setPerms.sh

    1. Run AFX start.
    2. Go back to the RSA Via L&G UI and check the status of AFX Connectors.

    Attachments

      Outcomes