Identity Manager JBoss Node Startup Fails with WFLYCTL0013 and WFLYCTL0080 java.lang.ExceptionInInitializerError
Article ID: 438016
Updated On:
Products
Issue/Introduction
A JBoss application server fails to start on specific nodes within a cluster. The customer observed that while most nodes start successfully, certain nodes fail during the deployment phase of the application. The following error is captured in the server logs:
ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "<war name>.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"<wat name>.war\".undertow-deployment" => "java.lang.ExceptionInInitializerError Caused by: java.lang.ExceptionInInitializerError Caused by: java.lang.NullPointerException"}}
The server eventually reports WFLYSRV0026: JBoss EAP started (with errors) but the critical services remain failed or missing dependencies.
Environment
CA Identity Suite / Identity Manager
Application Server: JBoss EAP 7.4.14.GA (WildFly Core 15.0.32.Final-redhat-00001)
Configuration: Multi-node cluster environment
Resolution
To resolve the startup failure, perform the following troubleshooting and maintenance steps on the affected nodes:
Stop the JBoss Service: Ensure the application server is completely shut down before proceeding.
Clear Temporary Directories: Delete all contents within the following directories to ensure a clean deployment
<JBOSS_HOME>/standalone/tmp/
<JBOSS_HOME>/standalone/data/
Identify and Remove Duplicate JARs: Inspect the WEB-INF/lib directory of the failing deployment (e.g., <war name>.war) and the JBoss modules. Ensure only one version of each library is present.
Validate JVM Configuration Files: If configuration files were recently edited, verify they do not contain Windows-style line endings or unreadable characters. It is recommended to recreate the files or use a tool like dos2unix if running on Linux.
Synchronize Deployment Files: Ensure the .war or .ear files on the failing nodes are identical to the versions on the working nodes. This might require copying the file from working node to non working one.
Restart JBoss: Start the server and monitor the server.log to confirm that all services start without error.
Feedback
