Oracle.security.jps.wls.listeners.JpsApplicationLifecycleListener Class not Found Exception

Oracle.security.jps.wls.listeners.JpsApplicationLifecycleListener Class not Found Exception

Error:

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

at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:280)

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.

Reference metalink Doc ID 1286039.1