AFX server fails to start with a message: WARNING!! Timed out waiting for AFX applications to start in RSA Identity Governance and Lifecycle

3 years ago

Originally Published: 2017-08-23

Article Number

000045558

Applies To

RSA Product Set: RSA Identity Governance and Lifecycle
RSA Version/Condition: All

Issue

AFX server fails to start with a message: WARNING!! Timed out waiting for AFX applications to start. Please check AFX application log files for detailed status information.
User-added image

Cause

This issue occurs because the host name in the afx-config.properties does not match with the actual host name.

Resolution

NOTE: Always take a backup before making any changes to a file.

Assuming that you have already tried the steps mentioned in KB-000029259 - RSA Identity Governance and Lifecycle Access Fulfillment Express (AFX) Server fails to start with message: WARNING!! Timed out waiting for AFX applications to start and still the AFX fails to start with the message: WARNING!! Timed out waiting for AFX applications to start. Please check AFX application log files for detailed status information.

Check for the below information in the mule_ee.log while starting the AFX:

2017-08-23 10:07:33.835 [INFO] com.aveksa.afx.server.init.ConfigureDefaultSSLContextComponent:75 - Loaded trusted certificate entries from '/home/oracle/AFX/mule/conf/client.keystore'
2017-08-23 10:07:33.843 [INFO] com.aveksa.afx.server.init.ConfigureDefaultSSLContextComponent:118 - Enabled SSL Protocol:TLSv1
2017-08-23 10:07:33.843 [INFO] com.aveksa.afx.server.init.ConfigureDefaultSSLContextComponent:118 - Enabled SSL Protocol:TLSv1.1
2017-08-23 10:07:34.205 [INFO] com.aveksa.afx.server.init.SubmitInitializationRequestComponent:46 - Initialization Request URL:https://rsa.aveksa.prod.com:8444/aveksa/afx/initialization
2017-08-23 10:07:34.214 [INFO] org.mule.module.client.MuleClient:197 - No existing ManagementContext found, creating a new Mule instance
2017-08-23 10:07:34.218 [INFO] org.mule.lifecycle.AbstractLifecycleManager:197 - Initialising RegistryBroker
2017-08-23 10:07:34.295 [INFO] org.mule.config.processors.DecoratingAnnotatedServiceProcessor:197 - org.mule.config.AnnotationsParserFactory implementation not found in registry, annotations not enabled
2017-08-23 10:07:34.320 [INFO] org.mule.lifecycle.AbstractLifecycleManager:197 - Initialising model: _muleSystemMode

Compare the Initialization Request URL with the host name of the current machine. If there is a difference in the host name in the log file, we need to make the below changes in the afx-config.properties to start the AFX successfully.

Till Version 7.0.0

Open a SSH session and cd to the AFX directory/mule/lib/user.
```
cd /home/oracle/AFX/mule/lib/user/
```
Do a listing in this location and open the "afx-config.properties".
Look for the "afx.config.acm.host=" in the afx-config-properties file.
Change the "afx.config.acm.host=" to the correct host name and save the changes.
Start the AFX and it should start successfully.

Post Version 7.0.1
From version 7.0.1 the mule directory is replaced with ESB.

Open a SSH session and cd to the AFX directory/esb/lib/user.
```
cd /home/oracle/AFX/esb/lib/user/
```
Follow the steps 2 to 4 mentioned above and it will start the AFX successfully.

Don't see what you're looking for?

Related Articles

Trending Articles