CODEWITHSUNDEEP
javaloggingweblogicjava.util.logging
Superman9999
Superman9999

Reputation: 825

java.util.logging.Logger log level is coming up as null

I am running into logging issues after upgrading my Java EE app from Weblogic/JDeveloper to 12.1.2 to 12.1.3.

System.out.println is printing to the server log fine but log.info("test") is not. The logging works if I set the log level e.g. log.setLevel(Level.INFO). Here are my test results.

// This works
System.out.println("test1");
// Output when run: test1

// This does not work. Nothing prints to the server log
log.info("test2");

// The above works if I set the log level
log.setLevel(Level.INFO);
log.info("test3");
// Output when run: test3

// This prints null. It appears that logging level is set to null on server startup
System.out.println(" what is my current logging level: " + log.getLevel());

As per Oracle documentation if no logging configuration is provided then the default logging.properties in JDK/JRE/Lib is used. The default log level is INFO.

I have also tried to load up logging.properties and switch log4j but nothing works.

I don't want to set log level to something in every class. Is there a way to set this on server startup or debug what is causing/setting the logging level to null.

Upvotes: 1

Views: 6714

Answers (1)

jmehrens
jmehrens

Reputation: 11085

From the logger documentation:

The result may be null, which means that this logger's effective level will be inherited from its parent.

So you only have to set the level of the root logger. You should check that a ConsoleHandler is installed and that the level is set to INFO or lower. You should also check that writing to System.err shows up in the log file as that is the stream that is used for the ConsoleHandler.

Upvotes: 0

Related Questions