-
1. Re: Startup classes cannot lookup Session Beans
dgriffin Jul 17, 2008 11:14 PM (in response to dgriffin)I did some things to move these lookups outside of @Startup components. Lookup still fail.
I see the exact jndi name I am trying to lookup in the log file when the SLSB was installed. Makes no sense. I see it but the top level lookup key is reported as not bound.
As in lookup(
ec20/b/c
) returns javax.naming.NameNotFoundException: ec20 not boundideas?
-
2. Re: Startup classes cannot lookup Session Beans
pmuir Jul 18, 2008 6:29 PM (in response to dgriffin)Please post code and a full stack trace.
-
3. Re: Startup classes cannot lookup Session Beans
alrubinger Jul 22, 2008 12:18 PM (in response to dgriffin)Please confirm in JNDIView that the SLSB is getting placed at
ec20/b/c
, like the logs report?S,
ALR -
4. Re: Startup classes cannot lookup Session Beans
dgriffin Jul 22, 2008 9:03 PM (in response to dgriffin)I have since determined this is not a Seam issue. It seems to be a 5.0.0RC1 issue. I moved the startup code into a servlet configured with load-on-startup and the problem still occurs. It looks like the app server is executing startup methods that need to use EJBs before the EJBs are bound in jndi. This is now posted in the JBoss EJB3 forum.
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165901#4165901