Each listener should be in it's own <listener> ... </listener> element block. Don't try to put all three in one.

--David

Ken Bowen wrote:
Hi all,

Using: Mac OS X 10.4.5 running Tomcat 5.5.26 -- this is a brand-new copy downloaded from Apache & unzipped; no changes.

This project used to work; I'm trying to figure out what got broken.

Symptom: listenerStart fails without even getting to the first line of the AppListener (catalina.out trace below).

From web.xml:

<web-app>
  <listener>
<listener-class>com.connectedtrading.listener.AppListener</listener-class> <listener-class>com.connectedtrading.database.HibernateListener</listener-class> <listener-class>com.connectedtrading.listener.SessionListener</listener-class>
  </listener>
.......

I've tried swapping the first two lines; neither works anymore.
Both listener classes are present in WEB-INF/classes.

My application context.xml is in META-INF:

<Context path="" debug="5" reloadable="true" crossContext="true">

<Resource name="jdbc/ct_alerts" auth="Container" type="javax.sql.DataSource"
        maxActive="100" maxIdle="30" maxWait="10000"
    username="xxxxx" password="xxxxx"
    driverClassName="com.mysql.jdbc.Driver"
    url="jdbc:mysql://localhost:3306/ct_alerts"
    validationQuery="select 1"
  />
</Context>

I've dropped raw println's at the beginning of the listeners, e.g.:

public void contextInitialized(ServletContextEvent servletContextEvent)
        {
System.out.println("++++++++++++++++++");
        .......

But as you can see from the catalina.out trace below, these are not being executed.


To eliminate possible permission problems, I've made the entire app tree in webapps universally read-write-executable (anyway, it's all owned by me and tomcat is running
as me -- started both from startup.sh or from Eclipse).

Any thoughts or pointers about working this out will be greatly appreciated:

Here's the startup trace from catalina.out:

Aug 6, 2008 11:07:40 AM 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: /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin:/Users/ken/Projects/bin/apache-tomcat-5.5.26/bin
Aug 6, 2008 11:07:40 AM org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Aug 6, 2008 11:07:40 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 673 ms
Aug 6, 2008 11:07:41 AM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Aug 6, 2008 11:07:41 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.26
Aug 6, 2008 11:07:41 AM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
Aug 6, 2008 11:07:41 AM org.apache.catalina.core.ApplicationContext log
INFO: org.apache.webapp.balancer.BalancerFilter: init(): ruleChain: [org.apache.webapp.balancer.RuleChain: [org.apache.webapp.balancer.rules.URLStringMatchRule: Target string: News / Redirect URL: http://www.cnn.com], [org.apache.webapp.balancer.rules.RequestParameterRule: Target param name: paramName / Target param value: paramValue / Redirect URL: http://www.yahoo.com], [org.apache.webapp.balancer.rules.AcceptEverythingRule: Redirect URL: http://jakarta.apache.org]] 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 11:07:42 AM org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
Aug 6, 2008 11:07:42 AM org.apache.catalina.core.StandardContext start
SEVERE: Context [/connectedtrading] startup failed due to previous errors
Aug 6, 2008 11:07:42 AM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: contextInitialized()
......

Thanks,
Ken



---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to