geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lin Sun (JIRA)" <>
Subject [jira] Created: (GERONIMO-1083) daytrader does not work with tomcat
Date Mon, 17 Oct 2005 14:16:45 GMT
daytrader does not work with tomcat

         Key: GERONIMO-1083
     Project: Geronimo
        Type: Bug
  Components: sample apps, Tomcat  
    Versions: 1.0-M5    
 Environment: Windows and Tomcat as the default web container
    Reporter: Lin Sun

when I deploy dayTrade with tomcat as the default web container, found below exceptions in
the logs, and I could not even get to the http://localhost:8080/daytrader page.

16:45:38,534 DEBUG [ContainerBase] Add child StandardWrapper[org_apache_geronimo_samples_daytrader_TradeWSAction]
16:45:38,537 ERROR [Digester] End event threw exception
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(
        at sun.reflect.NativeMethodAccessorImpl.invoke(
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(
... ...
Caused by: java.lang.NullPointerException
        at org.apache.catalina.core.StandardContext.addMessageDestinationRef(
        ... 95 more
16:45:38,541 ERROR [ContextConfig] Parse error in application web.xml
        at org.apache.tomcat.util.digester.Digester.createSAXException(
Compiled Code))
        at org.apache.tomcat.util.digester.Digester.createSAXException(
Compiled Code))
        at org.apache.tomcat.util.digester.Digester.endElement( Code))
16:45:38,543 DEBUG [ContextConfig] ======================
16:45:38,543 ERROR [ContextConfig] Marking this application unavailable due to previous error(s)
16:45:38,543 ERROR [StandardContext] Error getConfigured
16:45:38,543 ERROR [StandardContext] Context [/trade] startup failed due to previous errors

This is caused by the <message-destination-ref> tags inside the web.xml of tradeWeb.war.
  Somehow tomcat doesn't like it.  I tried to comment out the following and things started
to work again.   However,  without the <message-destination-ref> tags, the JMS resources
are not defined correctly.

<!-- <message-destination-ref id="MessageDestinationRef_1">
      <message-destination-ref id="MessageDestinationRef_2">
      </message-destination-ref>   -->

I don't mind digging more into this...any hint/advice is appreciated!

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message