tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dan Armbrust <>
Subject Re: How to debug Error: listenerStart?
Date Sat, 04 Apr 2009 17:45:09 GMT
On Fri, Apr 3, 2009 at 8:32 PM, Caldarale, Charles R
<> wrote:
>> From: Caldarale, Charles R
>> Subject: RE: How to debug Error: listenerStart?
>> To close out this thread
> Or maybe not.
>> I've reopened bug
>> and attached a war file which demonstrates the problem.
> I downloaded your a.war file into my Tomcat 6.0.18 installation on my Vista 64 box, and
got the following in localhost.2009-04-03.log:

Perhaps it is behaving different on Tomcat 6.  I didn't try 6, only
the latest 5.5, since that's what I'm using in production.

Also, your stack trace is showing that it was indeed, logged by
tomcat's loggers.  Did you try renaming the
file that I provided?  Does it still log the stack trace to Tomcat's
logger at that point, or does it log it to the log4j logger?  (The
output will look different if it was formatted by log4j)

I contend that it should never be printed by log4j, since that is
within the webapp which is failing - and tomcat can't know that log4j
has been configured.  But yet, on my system, that is exactly what is

> Note that the above appeared in the logs *only* after shutting down Tomcat, since something
is buffering the log entries and preventing them from being written > to the file system

I am doing a proper shutdown of Tomcat - so anything that isn't
flushed yet should be flushed during shutdown.  I'll check with tomcat
6 on Monday and see if it behaves differently.  I'm also still looking
into a (possibly?) related issue that I have where log4j in every
webapp deployed beyond the first fails to auto-configure.  But I
haven't yet figured out how to reproduce the issue that I'm seeing in
our large production apps in a small demo app.

> Remy's answer isn't going to be pretty...

Oh well.  I'm not concerned about the company I'd be keeping if I
(once again) get to join the masses of tomcat users that have had bugs
and surprisingly bad behavior declared non-bugs and perfectly normal
behavior by Remy.

Thanks for your help with this issue.


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

View raw message