Identity Manager is not starting after installing CHF1 (14.5.1 CHF1)
search cancel

Identity Manager is not starting after installing CHF1 (14.5.1 CHF1)

book

Article ID: 388327

calendar_today

Updated On:

Products

CA Identity Suite

Issue/Introduction

The customer applied CHF1 on top of v14.5 SP1. Post the installation, the Identity Manager is failing to start. The below-listed errors are seen in server.log

2025-02-11 15:46:13,654 ERROR [ims.llsdk.environment] (ServerService Thread Pool -- 127) Plugin specified an object type [IM SCREEN DEFINITION] for which there is already a provider in use. Ignoring this plugin.
2025-02-11 15:46:13,654 ERROR [ims.llsdk.environment] (ServerService Thread Pool -- 127) Plugin specified an object type [IM AUTH USER] for which there is already a provider in use. Ignoring this plugin.
2025-02-11 15:46:13,659 ERROR [ims.llsdk.environment] (ServerService Thread Pool -- 127) Plugin specified an object type [IM TAB DEFINITION] for which there is already a provider in use. Ignoring this plugin.
2025-02-11 15:46:13,659 ERROR [ims.llsdk.environment] (ServerService Thread Pool -- 127) Plugin specified an object type [IM TAB] for which there is already a provider in use. Ignoring this plugin.
2025-02-11 15:46:13,659 ERROR [ims.llsdk.environment] (ServerService Thread Pool -- 127) Plugin specified an object type [IM MOBJ ATTR DEF] for which there is already a provider in use. Ignoring this plugin.

2025-02-11 15:46:17,291 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 127) MSC000001: Failed to start service jboss.deployment.subunit."iam_im.ear"."user_console.war".undertow-deployment: org.jboss.msc.service.StartException in service jboss.deployment.subunit."iam_im.ear"."user_console.war".undertow-deployment: java.lang.LinkageError: loader constraint violation: loader (instance of org/jboss/modules/ModuleClassLoader) previously initiated loading for a different type with name "com/ca/commons/util/ByteData"
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:81) [wildfly-undertow-23.0.0.Final.jar:23.0.0.Final]
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_201]
    at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_201]
    at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) [jboss-threads-2.4.0.Final.jar:2.4.0.Final]
    at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990) [jboss-threads-2.4.0.Final.jar:2.4.0.Final]
    at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) [jboss-threads-2.4.0.Final.jar:2.4.0.Final]
    at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) [jboss-threads-2.4.0.Final.jar:2.4.0.Final]
    at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_201]
    at org.jboss.threads.JBossThread.run(JBossThread.java:513) [jboss-threads-2.4.0.Final.jar:2.4.0.Final]
Caused by: java.lang.LinkageError: loader constraint violation: loader (instance of org/jboss/modules/ModuleClassLoader) previously initiated loading for a different type with name "com/ca/commons/util/ByteData"
    at com.ca.identitymanager.plugins.IMEnvironmentInitializerPlugin.startEnvironment(IMEnvironmentInitializerPlugin.java:178)
    at com.netegrity.ims.businessprocess.IMSEnvironmentServiceImpl.startEnvironmentInternal(IMSEnvironmentServiceImpl.java:871)
    at com.netegrity.ims.businessprocess.IMSEnvironmentServiceImpl.startEnvironment(IMSEnvironmentServiceImpl.java:744)
    at com.netegrity.ims.bootstrap.Main.start(Main.java:340)
    at com.netegrity.webapp.SystemInitializer.contextInitialized(SystemInitializer.java:44)
    at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187) [undertow-servlet-2.2.5.Final.jar:2.2.5.Final]
    at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:219) [undertow-servlet-2.2.5.Final.jar:2.2.5.Final]
    at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:187) [undertow-servlet-2.2.5.Final.jar:2.2.5.Final]
    at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42) [undertow-servlet-2.2.5.Final.jar:2.2.5.Final]
    at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) [undertow-servlet-2.2.5.Final.jar:2.2.5.Final]
    at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105) [wildfly-undertow-23.0.0.Final.jar:23.0.0.Final]
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1530) [wildfly-undertow-23.0.0.Final.jar:23.0.0.Final]
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1530) [wildfly-undertow-23.0.0.Final.jar:23.0.0.Final]
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1530) [wildfly-undertow-23.0.0.Final.jar:23.0.0.Final]
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1530) [wildfly-undertow-23.0.0.Final.jar:23.0.0.Final]
    at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:255) [undertow-servlet-2.2.5.Final.jar:2.2.5.Final]
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:96) [wildfly-undertow-23.0.0.Final.jar:23.0.0.Final]
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:78) [wildfly-undertow-23.0.0.Final.jar:23.0.0.Final]
    ... 8 more

Environment

Standalone
v14.5.1 CHF1

Cause

1. It was discovered that the customer had placed backup files inside the <APP_SERVER>/standalone/deployment/ directory, for example:
   <APP_SERVER>/standalone/deployment/iam_im.ear.backup
   <APP_SERVER>/standalone/deployment/Backup
   <APP_SERVER>/standalone/deployment/content-backup-14.4.0

2. The WildFly Application Server was loading the same JAR file from multiple locations, causing it to be loaded multiple times.

Resolution

Remove all the backup files from <APP_SERVER>/standalone/deployment/ location. 

Backup files should not be stored in the /standalone/deployments directory. Instead, they should be kept in a secure, separate location.

Powered by Wolken Software