2013/9/16 Christopher Schultz <ch...@christopherschultz.net>: > On 9/13/13 10:08 PM, fachhoch wrote: >> One more interesting thing I added this server to my eclispe IDE >> and run from eclipse I don't get digester logs , but when run >> from console lots of digester logs. > > This corroborates my sense that your configuration is either incorrect > or not actually being read. > > I can't seem to find any information about how to get JULI into > "debug" mode itself (e.g. dump information about the log config > itself, and not just writing debug statements from other code). If you > can figure that out, it would be very helpful to diagnose your problem. > > Perhaps someone else on the list knows how to get JULI into debug mode? >
1. My guess is that there is "logging.properties" file somewhere in the webapp's classpath, as I mentioned. Apparently there is no internal logging in JULI (apart logging some unexpected errors), but you may a) run with a debugger (see Tomcat FAQ), b) recompile it with whatever debug statements you need. The configuration is loaded in org.apache.juli.ClassLoaderLogManager#readConfiguration(ClassLoader). 2. When you start Tomcat from within Eclipse IDE, by default it does not use Tomcat's org.apache.juli.ClassLoaderLogManager, but JRE's default java.util.logging.LogManager. Thus you are not using JULI. That is because Eclipse by default does not provide "-Djava.util.logging.manager" and "-Djava.util.logging.config.file" arguments to the JVM that it launches for Tomcat. Those are configurable. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
