AFX Server fails to start in a WebSphere deployment after upgrading to 7.0.x or higher of RSA Identity Governance & Lifecycle
Originally Published: 2017-09-28
Last Modified: 2023-11-30
Article Number
Applies To
RSA Version/Condition: 7.0.1, 7.0.2 7.1.x, 7.2.x
Platform/Application Server: WebSphere
Issue
The following errors are seen in the AFX log files:
- $AFX_HOME/esb/logs/esb.AFX-INIT.log
2017-09-20 17:06:04.117 [ERROR] com.aveksa.afx.server.init.SubmitInitializationRequestComponent:156 - Error submitting initialization request to RSA Identity Governance and Lifecycle server! 2017-09-20 17:06:04.117 [ERROR] com.aveksa.afx.server.init.SubmitInitializationRequestComponent:162 - Unable to establish secure (SSL) connection with RSA Identity Governance and Lifecycle server. 2017-09-20 17:06:04.118 [ERROR] com.aveksa.afx.server.init.SubmitInitializationRequestComponent:171 - SSL certificates for RSA Identity Governance and Lifecycle server and AFX were not issued by the same RSA Identity Governance and Lifecycle Certificate Authority(CA). You may encounter this problem if the RSA Identity Governance and Lifecycle certificate store has been changed, but either the RSA Identity Governance and Lifecycle server OR AFX installation hasn't been updated with the respective keystore containing new certificate and CA entries. Please update both the RSA Identity Governance and Lifecycle server and AFX installations with latest respective keystore available for download in the RSA Identity Governance and Lifecycle application. 2017-09-20 17:06:04.119 [ERROR] com.aveksa.afx.server.init.ServerInitializationComponent:79 - Server initialization failed! Please correct the issue and restart AFX. org.mule.api.transport.DispatchException: Failed to route event via endpoint: DefaultOutboundEndpoint{endpointUri=https://sedcasod0020.emea.isn.corpintra.net:8444/aveksa/afx/initialization, connector=HttpsConnector
- $AFX_HOME/esb/logs/mule_ee.log
ERROR 2017-09-12 16:07:44,357 [WrapperListener_start_runner] org.mule.module.launcher.DefaultArchiveDeployer: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + Failed to deploy artifact '10_AFX-INIT', see below + ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ org.mule.module.launcher.DeploymentInitException: CertPathBuilderException: Could not build a validated path. at org.mule.module.launcher.application.DefaultMuleApplication.init(DefaultMuleApplication.java:196) at org.mule.module.launcher.artifact.ArtifactWrapper$2.execute(ArtifactWrapper.java:62) at org.mule.module.launcher.artifact.ArtifactWrapper.executeWithinArtifactClassLoader(ArtifactWrapper.java:129) at org.mule.module.launcher.artifact.ArtifactWrapper.init(ArtifactWrapper.java:57) at org.mule.module.launcher.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:25) at org.mule.module.launcher.DefaultArchiveDeployer.guardedDeploy(DefaultArchiveDeployer.java:310) at org.mule.module.launcher.DefaultArchiveDeployer.deployArtifact(DefaultArchiveDeployer.java:330) at org.mule.module.launcher.DefaultArchiveDeployer.deployExplodedApp(DefaultArchiveDeployer.java:297) at org.mule.module.launcher.DefaultArchiveDeployer.deployExplodedArtifact(DefaultArchiveDeployer.java:108) at org.mule.module.launcher.DeploymentDirectoryWatcher.deployExplodedApps(DeploymentDirectoryWatcher.java:289) at org.mule.module.launcher.DeploymentDirectoryWatcher.start(DeploymentDirectoryWatcher.java:146) at org.mule.module.launcher.MuleDeploymentService.start(MuleDeploymentService.java:99) at org.mule.module.launcher.MuleContainer.start(MuleContainer.java:152) 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:606) at org.mule.module.reboot.MuleContainerWrapper.start(MuleContainerWrapper.java:52) at org.tanukisoftware.wrapper.WrapperManager$11.run(WrapperManager.java:4048) Caused by: org.mule.api.config.ConfigurationException: Error creating bean with name 'serverInitialization' defined in URL [file:/home/afxusr/AFX/esb/apps/10_AFX-INIT/mule-config.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.aveksa.afx.server.init.ServerInitializationComponent]: Constructor threw exception; nested exception is org.mule.api.lifecycle.InitialisationException: Server initialization failed! Please correct the issue and restart AFX.
- $AFX_HOME/esb/logs/esb.AFX-MAIN.log
2017-09-12 16:07:45.588 [ERROR] org.mule.module.launcher.application.DefaultMuleApplication:361 -
null java.lang.IllegalArgumentException: Could not resolve placeholder 'afx.server.activemq.password'
in string value "${afx.server.activemq.password}"
Cause
Resolution
- In the WebSphere console, navigate to Security > SSL certificate and key management > SSL configurations.
- Select the associated Aveksa SSL configuration.
- Under Additional Properties, select Quality of Protection (QoP) settings.
- Under Client authentication, select Required.
- Under Protocol, select TLSv1.2.
- Click OK to save the changes.
- Restart WebSphere.
Related Articles
Tables embedded in workflow email nodes are malformed after upgrading to version 7.1.1 of RSA Identity Governance & Lifecycle 88Number of Views RSA RADIUS Service stopped after upgrading to AM 8.6 262Number of Views Windows Share is not accessible from local users after upgrading to 8.5 263Number of Views RSA Identity Governance and Lifecycle IDC Unification is slow in "Step 8/10: Post-Processing: Populate Role Metrics" after… 119Number of Views Backup and scan for updates using NFS fails after upgrading to RSA Authentication Manager 8.4 326Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Unable to login to RSA Authentication Manager Security Console as super admin Manual synchronization introduced in RSA Authentication Manager 8.2 Service Pack 1 patch 6 Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory How to verify NTP server synchronization is not working in RSA Authentication Manager 8.x
Don't see what you're looking for?