After the migration of IM 14.5 Cent OS8 to Cent OS 9, Identity fails to start
Article ID: 401201
Updated On:
Products
Issue/Introduction
After the migration of IAM 14.5 Cent OS8 to Cent OS 9, Identity Manager was up and running. However after we placed the custom files and restarted the services Identity Manager is not starting with the following error.
2025-06-13 11:27:24,791 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "iam_im.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"iam_im.ear\".\"iam_im_identityminder_ejb.jar\".PARSE" => "WFLYSRV0153: Failed to process phase PARSE of subdeployment \"iam_im_identityminder_ejb.jar\" of deployment \"iam_im.ear\"
Caused by: org.jboss.msc.service.ServiceNotFoundException: service jboss.ejb.default-resource-adapter-name-service not found"}}
2025-06-13 11:27:24,816 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "undertow"),
("server" => "default-server"),
("host" => "default-host"),
("location" => "/")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.extension.undertow.handler.welcome-content"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.undertow.host.location.default-server.default-host./ is missing [org.wildfly.extension.undertow.handler.welcome-content]"]
Cause
Corruption or unreadable characters in the custom jvm_args.conf prevented the application server from reading the ca-standalone-full-ha.xml file, and instead was booting from the default, non-CA standalone-full.xml which prevented the deployment of the IM application.
In the process of the jvm_args.conf file being copied and edited in Windows and transferred to vAPP, we suspect that bad/unreadable characters were introduced which could not be read in Linux.
The clues to resolving the problem:
1. Reviewing the Wildfly startup in the server log and finding that the java options referencing ca-standalone-full-ha.xml were missing, for example:
Incorrect
sun.java.command = /opt/CA/wildfly-idm/jboss-modules.jar -mp /opt/CA/wildfly-idm/modules org.jboss.as.standalone -Djboss.home.dir=/opt/CA/wildfly-idm -Djboss.server.base.dir=/opt/CA/wildfly-idm/standalone -b ##.##.##.### -Djgroups.tcpping.initial_hosts=caim-srv-01[7600],caim-srv-02[7600] -[Djboss.node.name](http://djboss.node.name/)=iamnode1 -Djgroups.bind_addr= ##.##.##.### -Dnete.j2ee.vendor=jboss -Djava.net.preferIPv4Stack=true -Djboss.as.management.blocking.timeout=900 -u ##.##.##.### -Djboss.smtp.host=localhost
Correct
sun.java.command = /opt/CA/wildfly-idm/jboss-modules.jar -mp /opt/CA/wildfly-idm/modules org.jboss.as.standalone -Djboss.home.dir=/opt/CA/wildfly-idm -Djboss.server.base.dir=/opt/CA/wildfly-idm/standalone -b ##.##.##.### -Djgroups.tcpping.initial_hosts=caim-srv-01[7600],caim-srv-02[7600] -[Djboss.node.name](http://djboss.node.name/)=iamnode1 -Djgroups.bind_addr= ##.##.##.### -Dnete.j2ee.vendor=jboss -Djava.net.preferIPv4Stack=true -Djboss.as.management.blocking.timeout=900 -u ##.##.##.### -Djboss.smtp.host=localhost -Djboss.smtp.port=25 -c ca-standalone-full-ha.xml -bmanagement 0.0.0.0 -bprivate 0.0.0.0 -bunsecure 0.0.0.0
2. The client reported that the problem started after applying customizations, including jvm_args.conf.
Resolution
Resolved by manually editing jvm_args.conf with vi directly on the linux vAPP servers.
Feedback
