geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Hogstrom (JIRA)" <>
Subject [jira] Closed: (GERONIMO-1369) javax.ejb.NoSuchObjectLocalException in the ServletContextListener.contextInitialized() method
Date Fri, 16 Dec 2005 19:46:49 GMT
     [ ]
Matt Hogstrom closed GERONIMO-1369:

    Fix Version: 1.0
     Resolution: Fixed
      Assign To: Matt Hogstrom

This is the same issue as GERONIMO-1363.  We'll use this test case as well to confirm the
problem is resolved.  

> javax.ejb.NoSuchObjectLocalException in the ServletContextListener.contextInitialized()
> ----------------------------------------------------------------------------------------------
>          Key: GERONIMO-1369
>          URL:
>      Project: Geronimo
>         Type: Bug
>   Components: web
>     Versions: 1.0
>  Environment: Windows XP (SP2), Sun JDK build 1.4.2_08-b03
>     Reporter: Alexander Korostov
>     Assignee: Matt Hogstrom
>      Fix For: 1.0
>  Attachments:
> In my application, I lookup and invoke a session bean (via local interface) in the ServletContextListener.contextInitialized().
Sometimes application throws a NoSuchObjectLocalException in the ServletContextListener.contextInitialized(),
sometimes all works fine. This bug is appeared on both Tomcat and Jetty.
> I can not reproduce this bug with the 100% probability on the latest snapshot. Even if
I change the application a bit (rename the EJB or WEB project) this bug can disappear or appear
> It looks like some synchronization (racing conditions) problem: sometimes LocalHome of
my bean is published before the ServletContextListener.contextInitialized() invoked, sometimes
> See the attached geronimo.log and a test application. Note that the geronimo.log contains
both cases: 
> 1. when the application starts fine 
> 2. throws an exception.
> Sorry for the big size of the test application: I tried to minimize it, but only in the
current state I receive this bug with the 50% probability.
> Note that on M5 this bug is 100% reproducible in my environment.

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