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.xmlCaused by: Bean type class com.opensymphony.xwork2.ObjectFactory with the name struts has already been loaded by beanjavax.net.ssl.SSLHandshakeException: PKIX path building failedUT005023: Exception handling request to /iam/immanage/: Unable to load configuration. - Class: sun.security.ssl.Alert
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).
To resolve the conflict, identify and remove the duplicate older library files and clear the application server cache.