tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Konstantin Kolinko <>
Subject Re: JULI prefix not recognized?
Date Thu, 23 Jun 2011 23:47:31 GMT
2011/6/24 throwsCode <>:
> Hi Konstantin:
> I added the following argument to the Apache Tomcat Server Run
> Configuration:
> -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
> It worked just as you suggested it would; however, it requires the argument
> be placed in the VM arguments section.  I have many small clients that on
> occassion share VMs with other Tomcat Servers.  Is there a way to do the
> same without the Runtime Argument?


I am afraid that there is no other way.

This property configures java.util.logging implementation used by VM.

IIRC in java.util.logging there exists a method that allows to reset
logging configuration,  but I think it only allows to reconfigure
handlers, and does not support replacing LogManager at runtime.

You can look into JRE sources  to see at what time the value of
"java.util.logging.manager" property is being read.

(*) You may have better luck by configuring Tomcat to use log4j (see
relevant section in our logging.html).  With log4j you can go without
ClassLoaderLogManager and without, but there is one
   - Tomcat (using commons-logging) and webapps that use
commons-logging will detect presence of log4j and use it instead of
   - Any web-applications that use java.util.logging will try to use
default LogManager implementation, and will suffer from PermGen memory
leaks during redeployments and restarts. Because default LogManager
from JRE will keep their classes in memory.

The (*) is theory. I have not tested it in practice.

Best regards,
Konstantin Kolinko

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message