Jess Holle wrote:
Jess Holle wrote:
Okay, I did a bit more digging.
*If*:
* Your web app contains log4j.jar *and* commons-logging.jar.
* You do not have log4j installed in any of Tomcat's own lib
directories.
* You use a JNDI or other contextual classloader based
Remy Maucherat wrote:
Jess Holle wrote:
Jess Holle wrote:
Okay, I did a bit more digging.
*If*:
* Your web app contains log4j.jar *and* commons-logging.jar.
* You do not have log4j installed in any of Tomcat's own lib
directories.
* You use a JNDI or other contextual classloader
Jess Holle wrote:
Remy Maucherat wrote:
What's unexpected here is as you say that these loggers are static -- or
in any event not per-web-app. Otherwise, this behavior would be fine
and good!
Yes, I forgot about Jasper when I added the container loggers in 5.5 :(
At first when we added
Remy Maucherat wrote:
I also added fixes recently so that loggers are not accessed too
early, which was a similar issue (some loggers would be have be
improperly associated with the container classloader). There's lots of
tweaking needed with logging overall, it's sort of to be expected.
I'll
Remy Maucherat wrote:
Here, I suppose modifying all the loggers to be like this:
private Log log = LogFactory.getLog(JspServlet.class);
would fix the issue without further problems.
Hmm... Any chance of such a fix in the next few months. I can search
out such and suggest patches, but I'm quite
Jess Holle wrote:
Remy Maucherat wrote:
Jess Holle wrote:
Why out of curiosity? I don't have a pro-UGLI ax to grind here, but
Commons-Logging's behavior in Tomcat is really undesirable as is.
It would be the same anyway: the loading configuration and the logger
instances will be tied to the
Remy Maucherat wrote:
BTW, JBoss (supposedly, I didn't check personally) uses
commons-logging everywhere, and the logging implementation used is
log4j.
That works since *everything* uses log4j. The issue is with Tomcat
is really one of *not* having log4j at the Tomcat level but having it
in
Jess Holle wrote:
Remy Maucherat wrote:
BTW, JBoss (supposedly, I didn't check personally) uses
commons-logging everywhere, and the logging implementation used is
log4j.
That works since *everything* uses log4j. The issue is with Tomcat
is really one of *not* having log4j at the Tomcat level
I had e-mailed this to users mailing list, but I have what I believe is
a more dev follow-on question:
Is there a good way to get my own start/stop action called at a
per-VM level?
This is assuming I end up having to move log4j up into Tomcat's
classloaders -- at which point I'll
P.S. Why does Tomcat use Commons Logging rather than UGLI?
Jess Holle wrote:
I had e-mailed this to users mailing list, but I have what I believe
is a more dev follow-on question:
Is there a good way to get my own start/stop action called at a
per-VM level?
This is assuming I end up
UGLI is far from mature enough to be used by Tomcat at this point. When
log4j 1.3 is out, we'll see.
Yoav
-Original Message-
From: Jess Holle [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 17, 2005 4:17 PM
To: Tomcat Developers List
Subject: Re: Web apps vs. Logging vs. Tomcat
...
--
Jess Holle
Yoav Shapira wrote:
UGLI is far from mature enough to be used by Tomcat at this point. When
log4j 1.3 is out, we'll see.
Yoav
-Original Message-
From: Jess Holle [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 17, 2005 4:17 PM
To: Tomcat Developers List
Subject: Re: Web apps vs
-
From: Jess Holle [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 17, 2005 4:30 PM
To: Tomcat Developers List
Subject: Re: Web apps vs. Logging vs. Tomcat
Thanks. That answers that part of the question quite succinctly.
Now what remains is how can I work with log4j and commons logging
Yoav Shapira wrote:
UGLI is far from mature enough to be used by Tomcat at this point. When
log4j 1.3 is out, we'll see.
I already voted on that: -1.
Rémy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
Remy Maucherat wrote:
Yoav Shapira wrote:
UGLI is far from mature enough to be used by Tomcat at this point. When
log4j 1.3 is out, we'll see.
I already voted on that: -1.
Why out of curiosity? I don't have a pro-UGLI ax to grind here, but
Commons-Logging's behavior in Tomcat is really
:[EMAIL PROTECTED]
Sent: Thursday, March 17, 2005 4:30 PM
To: Tomcat Developers List
Subject: Re: Web apps vs. Logging vs. Tomcat
Thanks. That answers that part of the question quite succinctly.
Now what remains is how can I work with log4j and commons logging --
commons logging's behavior vis-a-vis
- Original Message -
From: Jess Holle [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Thursday, March 17, 2005 2:25 PM
Subject: Re: Web apps vs. Logging vs. Tomcat
Just one more stupid question:
How/where would I register/deregister (start/stop
Bill Barker wrote:
- Original Message -
From: Jess Holle [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Thursday, March 17, 2005 2:25 PM
Subject: Re: Web apps vs. Logging vs. Tomcat
Just one more stupid question:
How/where would I register/deregister
Jess Holle wrote:
Why out of curiosity? I don't have a pro-UGLI ax to grind here, but
Commons-Logging's behavior in Tomcat is really undesirable as is.
It would be the same anyway: the loading configuration and the logger
instances will be tied to the webapp classloader. It has to work this
- Original Message -
From: Jess Holle [EMAIL PROTECTED]
To: Tomcat Developers List tomcat-dev@jakarta.apache.org
Sent: Thursday, March 17, 2005 3:12 PM
Subject: Re: Web apps vs. Logging vs. Tomcat
Bill Barker wrote:
- Original Message -
From: Jess Holle [EMAIL PROTECTED
Hi,
Yoav Shapira wrote:
UGLI is far from mature enough to be used by Tomcat at this point. When
log4j 1.3 is out, we'll see.
I already voted on that: -1.
Rémy
Yup, I know. I'm holding out for the possibility that UGLI will be a good
enough solution and a significant enough
Remy Maucherat wrote:
Jess Holle wrote:
Why out of curiosity? I don't have a pro-UGLI ax to grind here, but
Commons-Logging's behavior in Tomcat is really undesirable as is.
It would be the same anyway: the loading configuration and the logger
instances will be tied to the webapp classloader.
Bill Barker wrote:
You just need to provide the methods (if you wanted to code against
Catalina, you'd just create a LifecycleListener :). This is a hook into
commons-modeler, so you technically could use a plain old JavaBean.
Otherwise, DynamicMBeans probably work best (or, at least give you the
23 matches
Mail list logo
