That's what's frustrating. I'm using a new Tomcat unzip with simple
JULI logging, so the files of interest are catalina.out
and catalina.2008-08-06.log, which are essentially identical.
Normally when a listener class fails, the trace is
shown in catalina.out, before/after the "Error listenerStart" line.
But nothing like that is appearing now.
That's why I threw in a System.out.println at the very beginning of
the listener to see that it was being entered.
But that print to out doesn't appear to being executed. I also think
that (in the past) when the listener class was
missing or not accessible, a "Class Not Found" exception was thrown
(and visible). But that isn't occurring either.
At the risk of repetition, here's the start up trace (repeated a few
minutes ago):
Aug 6, 2008 1:51:19 PM org.apache.catalina.core.AprLifecycleListener
lifecycleEvent
INFO: The Apache Tomcat Native library which allows optimal
performance in production environments was not found on the
java.library.path: .:/Library/Java/Extensions:/System/Library/Java/
Extensions:/usr/lib/java
Aug 6, 2008 1:51:19 PM org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Aug 6, 2008 1:51:19 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 485 ms
Aug 6, 2008 1:51:20 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Aug 6, 2008 1:51:20 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.26
Aug 6, 2008 1:51:20 PM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
log4j:WARN No appenders could be found for logger
(org.apache.commons.digester.Digester.sax).
log4j:WARN Please initialize the log4j system properly.
Aug 6, 2008 1:51:20 PM org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
Aug 6, 2008 1:51:20 PM org.apache.catalina.core.StandardContext start
SEVERE: Context [/connectedtrading] startup failed due to previous
errors
Aug 6, 2008 1:51:20 PM org.apache.coyote.http11.Http11BaseProtocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
Aug 6, 2008 1:51:21 PM org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
Aug 6, 2008 1:51:21 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/11 config=null
Aug 6, 2008 1:51:21 PM org.apache.catalina.storeconfig.StoreLoader load
INFO: Find registry server-registry.xml at classpath resource
Aug 6, 2008 1:51:21 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 1141 ms
--Ken
On Aug 6, 2008, at 1:09 PM, Mark Thomas wrote:
Ken Bowen wrote:
Ok, I fixed that (see below), but that does seem to change the
problem at all. The catalina.out trace is the same.
Have a look at the files in the logs directory. One of them should
have more information (like the stacktrace from the failed listener).
Mark
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
