Actually all the ejbs are in one jar, but I do use ejb-refs. The jndi failure
occurs in the bmp entity bean looking up either datasources or environment
variables. The bmp entity bean is created by a stateful session bean from the
same jar. It might fail on lookup of other ejbs but the app didn't get that
far before the first lookup failed. The client calling the sesion bean is
external though (Separate Tomcat VM process). I had problems with using the
EmbeddedTomService but thats another story :-(
I'm trying to track that problem down. Looks like it's classloader related
though.
Richard Backhouse
Oak Grove Software
Sebastien Alborini wrote:
> Richard Backhouse wrote:
> >
> > I found a bug in the new binary :
> >
> > It seems that that the new binary has changed the standardjboss.xml to
> > turn container optimization on by default on all the container
> > configurations. This causes my beans to fail in any of their jndi
> > lookups on "java:comp/env" objects. When I changed the optimize flag to
> > false in the standardjboss.xml they work again. I have stateful session
> > beans calling bmp entity beans. It seems that the bmp entity beans have
> > the problem.
> >
> > Richard Backhouse
> > Oak Grove Software
>
> Aargh,
>
> If this is an external ejb-ref, the two applications are distributed as
> separate jars, each one has its own classloader, and they are not
> shared.
>
> Solutions:
> - turn optimization off (you found this one)
> - put everything in the same jar, don't use external ejb-ref,
> optimization will work
> - let's redesign the classloaders to work with several jars
>
> Sebastien
