Is it possible to change log4j trace level without restart of WebLogic or GlassFish?

Question

Is it possible to change log4j trace level without restart of WebLogic or GlassFish?
We use -Dlog4j.configuration JVM argument to set log4j config file.
And now neither WebLogic or GlassFish reloads changes if log4j.xml was modified.

In JBoss(at least in JBoss 5.1) there is service org.jboss.logging.Log4jService which allows to set how frequently in seconds the log4j configuration file is checked for changes.
Is there something like this in WebLogic and GlassFish?

score 0 · Accepted Answer · edited May 23 '17 at 11:43

0

Yes it is possible.There is more than one approach depending on what you are doing with your app.

You can change it in the admin console by going to the managed server's logging tab. This is for the server output itself, not for apps running on the server.

Using WLST check here (it will involve a fair amount of work): http://www.theserverlabs.com/blog/2010/04/22/dynamically-changing-log-level-with-weblogic-log4j-jmx-and-wlst/

Setting it via code in an app: Dynamically Changing log4j log level

edited May 23 '17 at 11:43

Community

1
1

answered Apr 18 '13 at 16:04

Display Name is missing

6,197
3
34
46

Caution: configureAndWatch method is unsafe for use in J2EE environments due to a Thread leak. – Volodymyr Bezuglyy Apr 18 '13 at 16:16
In case of using wlst changes will be lost after restarting of server. So in this case I need to change configuration using WLST and do the same changes in log4j.xml. – Volodymyr Bezuglyy Apr 18 '13 at 16:17

Is it possible to change log4j trace level without restart of WebLogic or GlassFish?

1 Answers1