My Oracle Support Banner

"Error: Could not find or load main class =" When Starting Managed Server (Doc ID 2912041.1)

Last updated on APRIL 29, 2024

Applies to:

Oracle Utilities Network Management System - Version 2.3.0.2.0 and later
Oracle Network Management for Utilities - DMS - Version 2.3.0.2.0 and later
Information in this document applies to any platform.

Symptoms

On : 2.5.0.2.0 version, NMS Infrastructure

The NMS Server failed to start.
The managed server log had this:

Starting WLS with line:
/usr/jdk/jdk1.8.0_191/bin/java -server   -Xms256m -Xmx512m -XX:CompileThreshold=8000 -cp <WL_HOME>/server/lib/weblogic-launcher.jar -Dlaunch.use.env.classpath=true -Dweblogic.Name=nms -Djava.security.policy=<WL_HOME>/server/lib/weblogic.policy -Dweblogic.system.BootIdentityFile=<DOMAIN_HOME>/servers/nms/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.nmservice.RotationEnabled=true -Xms8192m  -Xmx8192m  -XX:PermSize=1024m  -XX:MaxPermSize=1024m  -XX:+UseConcMarkSweepGC  -XX:+ExplicitGCInvokesConcurrent  -javaagent:lib/nms_monitor.jar  -Dweblogic.jndi.allowGlobalResourceLookup=true  -Dweblogic.jndi.allowExternalAppLookup=true  -Doracle.xdkjava.security.resolveEntityDefault=false  -d64 -DintersysName=InterSys_nmsadmin -Dlog4j.configurationFile=<DOMAIN_HOME>/nms-log4j.xml -DUseSunHttpHandler=true -Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl -Dweblogic.MaxMessageSize = 50000330 -Djava.system.class.loader=com.oracle.classloader.weblogic.LaunchClassLoader  -javaagent:<WL_HOME>/server/lib/debugpatch-agent.jar -da -Dwls.home=<WL_HOME>/server -Dweblogic.home=<WL_HOME>/server -Dweblogic.management.server=http://<IP ADDRESS>:<PORT>   weblogic.Server
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=1024m; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=1024m; support was removed in 8.0
Error: Could not find or load main class =
Stopping Derby server...
Derby server stopped.
<Nov 22, 2022 4:44:31 PM IST> <INFO> <NodeManager> <The server 'nms' with process id 1852605 is no longer alive; waiting for the process to die.>
<Nov 22, 2022 4:44:31 PM IST> <FINEST> <NodeManager> <Process died.>
<Nov 22, 2022 4:44:31 PM IST> <INFO> <NodeManager> <Server failed during startup. It may be retried according to the auto restart configuration.>
<Nov 22, 2022 4:44:31 PM IST> <FINEST> <NodeManager> <get latest startup configuration before deciding/trying to restart the server>
<Nov 22, 2022 4:44:31 PM IST> <INFO> <NodeManager> <Server failed but will not be restarted because the maximum number of restart attempts has been exceeded>



Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.