DO NOT REPLY [Bug 34110] The message SEVERE: Error listenerStart should be more explicit
https://issues.apache.org/bugzilla/show_bug.cgi?id=34110 Mark Thomas ma...@apache.org changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||WONTFIX --- Comment #7 from Mark Thomas ma...@apache.org 2009-06-10 08:38:22 PST --- This clash between commons-logging in a webapp and in Tomcat is one of the reasons for the switch to JULI in Tomcat 6. I can reproduce this on 5.5.x but I can't see how to fix it without some major changes (ie porting JULI). That is just too big a chance for a branch as mature as 5.5.x. As an aside, r374893 ( https://svn.apache.org/viewcvs.cgi?view=revrev=374893 ) makes it clear that it is intentional that the logger is loaded by the web application classloader. You do get a warning that log4j is not configured properly which at least gives you a clue that you are missing some log information. I am therefore closing this as won't fix. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 34110] The message SEVERE: Error listenerStart should be more explicit
https://issues.apache.org/bugzilla/show_bug.cgi?id=34110 Wesley topo...@gmail.com changed: What|Removed |Added CC||topo...@gmail.com -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 34110] The message SEVERE: Error listenerStart should be more explicit
https://issues.apache.org/bugzilla/show_bug.cgi?id=34110 --- Comment #6 from Dan Armbrust daniel.armbrust.l...@gmail.com 2009-04-06 07:58:11 PST --- This issue does not occur under Tomcat 6.0.18. I believe that Charles has the correct explanation for what is going on: http://marc.info/?l=tomcat-userm=123889737632345w=2 -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 34110] The message SEVERE: Error listenerStart should be more explicit
https://issues.apache.org/bugzilla/show_bug.cgi?id=34110 --- Comment #4 from Dan Armbrust daniel.armbrust.l...@gmail.com 2009-04-03 11:45:41 PST --- Created an attachment (id=23439) -- (https://issues.apache.org/bugzilla/attachment.cgi?id=23439) webapp which reproduces the error My comment #3 was missing a step that is required to reproduce this problem. You need to have log4j and commons-logging.jar in your war file to reproduce the issue. This war file will fail to deploy due to an invalid listener in tomcat 5.5.27, and fails to log the stack trace containing the cause of the problem anywhere. The only output given is: SEVERE: Error listenerStart SEVERE: Context [/a] startup failed due to previous errors After tomcat has expanded the warfile, if you rename webapps/a/WEB-INF/classes/log4j.properties.hidden to log4j.properties - then you will get a stack trace - but only because it has been sent to the logger within the webapp. It doesn't get sent to tomcats logging system. I don't understand why tomcat is changing how it logs, depending on if log4j and commons-logging are present in the classpath of a webapp being deployed. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 34110] The message SEVERE: Error listenerStart should be more explicit
https://issues.apache.org/bugzilla/show_bug.cgi?id=34110 Dan Armbrust daniel.armbrust.l...@gmail.com changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID | --- Comment #5 from Dan Armbrust daniel.armbrust.l...@gmail.com 2009-04-03 11:47:38 PST --- I believe my attachment should be enough to support reopening this bug. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 34110] The message SEVERE: Error listenerStart should be more explicit
https://issues.apache.org/bugzilla/show_bug.cgi?id=34110 --- Comment #3 from Dan Armbrust daniel.armbrust.l...@gmail.com 2009-04-02 13:48:36 PST --- I ran into this issue where tomcat was not giving me any information to go on with one of my webapps. After a long search, documented here: http://marc.info/?t=12386172052r=1w=2 we discovered that the sequence of events which leads tomcat to not log any debug information about the error is as follows: You deploy a war file to tomcat which includes log4j.jar, and has a listener declared in the web.xml file. The listener in the web.xml file points to a class that doesn't exist. This will cause the deployment to fail. The war file that you deploy does _NOT_ include a log4j.properties or log4j.xml file in the WEB-INF/classes folder - presumably because your webapp dynamically configures log4j in a different manner. The end result is, there is some period of time during deployment of the webapp when tomcat attempts to log deployment messages to log4j which was supplied by your webapp - but since the log4j within the webapp is not yet configured, the messages are lost. I'm not sure if there is anything that can be done to improve this situation. An obvious solution for me is to supply a log4j.properties file which will be used to configure log4j for the short period of time before my dynamic configuration runs. But it seems like Tomcat should always log issues during deployment into its own logging system, rather than trying to send them into the webapps logging system. Here is a vote to re-open this bug. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 34110] The message SEVERE: Error listenerStart should be more explicit
https://issues.apache.org/bugzilla/show_bug.cgi?id=34110 Dan Armbrust daniel.armbrust.l...@gmail.com changed: What|Removed |Added CC||daniel.armbrust.l...@gmail. ||com -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
