> From: Alex Hooper [mailto:ahoo...@bmjgroup.com] > Subject: Re: logging failure with tomcat 6.0.29, jvm 1.6.0_30-b12, ubuntu > 10.04.3 LTS
> We've not modified it, though, so should be as per dist. It appears to be as you say. Looking at the stack trace a bit more: > java.lang.ClassNotFoundException: 1catalina.org.apache.juli.FileHandler > ... > at > java.util.logging.LogManager.loadLoggerHandlers(LogManager.java:345) > ... > at java.util.logging.Logger.getLogger(Logger.java:287) > at sun.management.snmp.util.MibLogger.<init>(MibLogger.java:57) > at sun.management.snmp.util.MibLogger.<init>(MibLogger.java:42) > at > sun.management.jmxremote.ConnectorBootstrap.<clinit>(ConnectorBootstrap.java:760) > at sun.management.Agent.startAgent(Agent.java:127) > at sun.management.Agent.startAgent(Agent.java:239) It appears that the JMX agent is using Tomcat's logging.properties but with the unmodified java.util.logging package from the JRE rather than JULI from Tomcat. Can you show us what the eventual command line is that launches Tomcat? The parameter specifying -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager looks like it's missing. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
