geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dain Sundstrom (JIRA)" <...@geronimo.apache.org>
Subject [jira] Updated: (GERONIMO-1655) Daytrader MDBs do not start properly
Date Thu, 06 Apr 2006 19:03:25 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-1655?page=all ]

Dain Sundstrom updated GERONIMO-1655:
-------------------------------------

    Component: sample apps

> Daytrader MDBs do not start properly
> ------------------------------------
>
>          Key: GERONIMO-1655
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1655
>      Project: Geronimo
>         Type: Bug
>     Security: public(Regular issues) 
>   Components: sample apps
>     Versions: 1.1
>  Environment: All (j2ee-jetty-server and j2ee-tomcat-server, rev 380210) 
>     Reporter: Anita Kulshreshtha
>      Fix For: 1.1

>
> The following MDBs of Daytrader application do not start during startup of the server
: 
> .................................................................
> WARNING: Some GBeans were not started successfully:
>     TradeStreamerMDB (starting)
>     TradeBrokerMDB (starting) 
>      This affects both jetty and tomcat servers.
>     These are waiting for MdbContainer to start, which in turn is waiting for Timers
. All the timers NonTransactionalThreadPooledTimer etc are being started properly,  but MdbContainer
is looking for non existent GBeans, i.e. the name part of the reference is NonTransactionalThreadPooledTimer,*
 Here is an example :
> 13:00:24,437 DEBUG [GBeanSingleReference] Waiting to start geronimo.server:J2EEApplication=null,J2EEModule=geronimo/openejb/1.1-SNAPSHOT/car,J2EEServer=geronimo,j2eeType=MdbContainer,name=MdbEjbContainer
because no targets are running for reference NontransactedTimer matching the patterns geronimo.server:J2EEApplication=null,J2EEServer=geronimo,j2eeType=GBean,name=NonTransactionalThreadPooledTimer,*


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message