Identity Manager Management Console Failure with ConfigurationException After Upgrade or Patch
search cancel

Identity Manager Management Console Failure with ConfigurationException After Upgrade or Patch

book

Article ID: 272077

calendar_today

Updated On:

Products

CA Identity Suite CA Identity Manager

Issue/Introduction

After upgrading Identity Manager or applying a patch, the User Console functions normally, but the Management Console (/iam/immanage/) fails to load and returns a "500 Internal Server Error." This issue is typically caused by conflicting versions of library files (e.g., Struts, Spring) in the deployment folder, often resulting from manual patch applications rather than using the Patch Deployer Tool.

The following errors are observed in the server.log:

  • ERROR [org.apache.struts2.dispatcher.Dispatcher] Dispatcher initialization failed com.opensymphony.xwork2.config.ConfigurationException: Unable to load configuration.
  • Caused by: com.opensymphony.xwork2.config.ConfigurationException: Unable to load vfs:/.../management_console.war/WEB-INF/lib/struts2-core-x.x.x.jar/struts-default.xml
  • Caused by: Bean type class com.opensymphony.xwork2.ObjectFactory with the name struts has already been loaded by bean
  • javax.net.ssl.SSLHandshakeException: PKIX path building failed
  • UT005023: Exception handling request to /iam/immanage/: Unable to load configuration. - Class: sun.security.ssl.Alert

 

 

Environment

  • Identity Manager: 14.4, 14.5
  • Application Server: Wildfly 15.0.1, Wildfly 23.0.2, JBoss EAP 7.4.0
  • Java: 1.8.0

Cause

Multiple versions of the same library JAR files exist in the deployment directories. When the application server attempts to initialize the Management Console, it encounters conflicting bean definitions from different versions of the same library (e.g., struts2-core-2.5.22.jar vs struts2-core-2.5.30.jar).

Resolution

To resolve the conflict, identify and remove the duplicate older library files and clear the application server cache.

  • Stop the Identity Manager (Wildfly/JBoss) service.
  • Identify and remove conflicting JAR files:
  • Navigate to the Management Console library directory: [WILDFLY_HOME]/standalone/deployments/iam_im.ear/management_console.war/WEB-INF/lib/
  • Search for duplicate versions of the following libraries:
    • struts2-core-.jar (e.g., keep 6.7.0 or 2.5.33, remove 2.5.x or 2.5.31)
    • freemarker-.jar
    • ognl-.jar
    • javassist-.jar
  • Navigate to the Identity Manager library directory: [WILDFLY_HOME]/standalone/deployments/iam_im.ear/library/
  • Check for duplicate Spring framework libraries:
    • spring-aop-.jar, spring-beans-.jar, spring-context-.jar, spring-core-.jar, etc.
  • Action: Move all older versions to a backup directory outside of the Wildfly installation path.
  • Clear Temporary Files:
    • Navigate to [WILDFLY_HOME]/standalone/
    • Delete the entire contents of the /tmp/ directory.
  • Restart the Identity Manager service.