java.lang.ClassNotFoundException: oracle.security.jps.wls.listeners.JpsApplicationLifecycleListener

1286039.1 Click to add to Favorites Managed Server Fails to Restart with ClassNotFoundException After Deploying the Imaging Application IPM 11g (Doc ID 1286039.1) To BottomTo Bottom In this Document Symptoms Changes Cause Solution Applies to: Oracle Weblogic Server - Version 10.3.3 and later Information in this document applies to any platform. ***Checked for relevance on 5-Oct-2012*** Symptoms A managed server fails to start from the console with the following exception, after deploying an imaging application on IPM 11g. The server starts correctly when invoking the default start up scripts. It only fails when started through console using a node manager. The following error message is reported in the log file as the cause for the deployment failure: Caused By: java.lang.ClassNotFoundException: oracle.security.jps.wls.listeners.JpsApplicationLifecycleListener at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:280) Changes An imaging enterprise application (.ear file) was deployed in the IPM 11g environment. Cause The issue is caused because the required classes are not loaded in the classpath when starting the servers using the nodemanager; that is, the nodemanager is used when starting managed servers through console. In the nodemanager.properties files the following settings are set to false, and as a result the servers are not using the classes present in the start up script. StartScriptEnabled=false When the servers directly usie the startWeblogic.sh or startManagedweblogic.sh scripts, instead of via nodemanager, the servers start up correctly. This is because all the required classes are present in the classpath when using the scripts for starting the server. Solution Force the classpath to be set to the desired value when starting the server through the node manager. To achieve this, the most recommended and easy solution is to set the node manager to use startup scripts while starting the managed server. You can execute the following steps to implement the above solution: Open the nodemanager.properties file Set the following properties to 'true': StartScriptEnabled=true StopScriptEnabled=true Stop the Admin Server and other servers in the domain that are running. Restart the nodemanager. Start the Admin Server Retest the issue by restarting the managed server through the console. Migrate the solution as appropriate to other environments.