Re: per-webapp logging problem with Tomcat 5.5

Remy Maucherat wrote: Could it be that all libraries I use go to the wrong log? All your libraries, like Spring, will use their own logger names. All these loggers are not defined in your configuration, so will all use the handlers for the root logger (.handlers).

Re: per-webapp logging problem with Tomcat 5.5

Boris Unckel wrote: Could it be that all libraries I use go to the wrong log? This depends on the common and shared classloader. Please put any JAR which is not delivered by Tomcat and already there in a default installation in your WEB-INF/lib folder. Test again. I don't understand. The

Re: per-webapp logging problem with Tomcat 5.5

Hello Andreas, I have read your response to Remy's mail. Could it be that all libraries I use go to the wrong log? This depends on the common and shared classloader. Please put any JAR which is not delivered by Tomcat and already there in a default installation in your WEB-INF/lib

Re: per-webapp logging problem with Tomcat 5.5

Boris Unckel wrote: You want to have a _one_ central place for your log configuration _and_ the correct logging just for that application - currently impossible. I would not necessarely say that logging has to be configured in one central place/file, but I think putting logging config _into_

Re: per-webapp logging problem with Tomcat 5.5

Hello, Thanks for your explanation about why real per-webapp logging is currently not possible with Tomcat 5.5 and Juli/java.util.logging. Is it the same with Log4J? Yes, naturally. You would have to place log4j.jar into your WEB-INF/lib and the configuration into the webapp to get logger

Re: per-webapp logging problem with Tomcat 5.5

Hi, I have a workaround: You provide a logging.properties in your webapp. All relevant parameters are controlled per system -D properties. With x4juli this will work for all webcontainers. Regards Boris - To unsubscribe,

Re: per-webapp logging problem with Tomcat 5.5

On 2/27/06, Andreas Schildbach [EMAIL PROTECTED] wrote: Boris Unckel wrote: I have a workaround: You provide a logging.properties in your webapp. All relevant parameters are controlled per system -D properties. A workaround for what? Providing a logging.properties in my webapp is

Re: per-webapp logging problem with Tomcat 5.5

Hi, Boris Unckel wrote: I have a workaround: You provide a logging.properties in your webapp. All relevant parameters are controlled per system -D properties. A workaround for what? Providing a logging.properties in my webapp is exactly what I'm trying to avoid. What's the relevant

Re: per-webapp logging problem with Tomcat 5.5

Remy Maucherat wrote: Very funny. Funny what? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: per-webapp logging problem with Tomcat 5.5

Hi Boris, I have now switched my server to one-properties-per-webabb (inside webapp dir). It's not nice, but it works. Thanks a lot for your help. Regards, Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For

Re: per-webapp logging problem with Tomcat 5.5

Hello, Andreas Schildbach wrote: My problem is, there is no logging going to any logfile. What am I doing wrong? Do I need to have unique numbers as a prefix to app1 and app2? (could I use 0app1 and 0app2?) I could not see any error but one: handlers =

Re: per-webapp logging problem with Tomcat 5.5

Hello Boris, thanks for your answer. I could not see any error but one: handlers = 1catalina.org.apache.juli.FileHandler, 2localhost.org.apache.juli.FileHandler, 3app1.org.apache.juli.FileHandler, 4app2.org.apache.juli.FileHandler, java.util.logging.ConsoleHandler as first line (aside from

Re: per-webapp logging problem with Tomcat 5.5

Good Morning Andreas, Andreas Schildbach wrote: Hello Boris, thanks for your answer. I could not see any error but one: handlers = 1catalina.org.apache.juli.FileHandler, 2localhost.org.apache.juli.FileHandler, 3app1.org.apache.juli.FileHandler, 4app2.org.apache.juli.FileHandler,

Re: per-webapp logging problem with Tomcat 5.5

On 2/26/06, Andreas Schildbach [EMAIL PROTECTED] wrote: Could it be that all libraries I use go to the wrong log? All your libraries, like Spring, will use their own logger names. All these loggers are not defined in your configuration, so will all use the handlers for the root logger

per-webapp logging problem with Tomcat 5.5

Hello everyone, I despair of configuring per-webapp logging for Tomcat 5.5, something that was easily possible with swallowOutput on pre-5.5 Tomcats. I've got 2 hosts (app1.de, app2.de), containing one context each. In addition, there is also the localhost context from the example