Could not set WebLogic node manager log level to DEBUG

Question

The exception dumped on STDOUT is:

Jul 6, 2011 12:17:00 PM weblogic.nodemanager.server.NMServer main
SEVERE: Fatal error in node manager server
weblogic.nodemanager.common.ConfigException: Invalid log level value 'DEBUG' for property 'LogLevel"
        at weblogic.nodemanager.server.NMServerConfig.getLevelProperty(NMServerConfig.java:218)
        at weblogic.nodemanager.server.NMServerConfig.<init>(NMServerConfig.java:159)
        at weblogic.nodemanager.server.NMServer.init(NMServer.java:176)
        at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:141)
        at weblogic.nodemanager.server.NMServer.main(NMServer.java:337)
        at weblogic.NodeManager.main(NodeManager.java:31)

Answer 1

Node manager is using log levels from java.util.logging.Level, and it is not using those used by WebLogic Server as it is documented by Oracle (com.bea.logging.LogLevel). The LogLevel property from nodemanager.properties can be set to: SEVERE, WARNING, INFO (default for WL Node Manger), CONFIG, FINE, FINER, FINEST, ALL and OFF.

LogLevel can be set also in the NodeManager startup script WL_SERVER/server/bin/startNodeManager.sh:

JAVA_OPTIONS="$JAVA_OPTIONS -DLogLevel=ALL"

See:

• http://download.oracle.com/docs/cd/E12840_01/wls/docs103/nodemgr/java_nodemgr.html#wp1070273
• http://download.oracle.com/docs/cd/E14571_01/apirefs.1111/e13941/com/bea/logging/LogLevel.html
• http://download.oracle.com/javase/6/docs/api/java/util/logging/Level.html

Answer 2

Looks like you are not the only one who has found this.

Even though the documentation says

Node Manager uses the same logging levels as WebLogic Server.

There are several forum posts out there that report the same problem.