anonymous wrote : 2008-07-21 14:51:17,851 INFO [org.jboss.ejb3.EJBContainer] (main) STARTED EJB: com.pearson.ejb3.session.DBUtilBean ejbName: DBUtilBean This is the point where the JNDI binding happens. You can confirm that in the server.log file, which will contain something like: | 2008-07-01 14:38:01,359 INFO [org.jboss.ejb3.EJBContainer] (main) STARTED EJB: org.myapp.ejb.impl.UserManagerBean ejbName: UserManagerBean | 2008-07-01 14:38:01,437 DEBUG [org.jboss.ejb3.proxy.factory.ProxyFactoryHelper] (main) Obtaining JNDI name from policy org.jboss.ejb3.jndipolicy.impl.PackagingBasedJndiBindingPolicy | 2008-07-01 14:38:01,437 DEBUG [org.jboss.ejb3.proxy.factory.ProxyFactoryHelper] (main) Obtaining JNDI name from policy org.jboss.ejb3.jndipolicy.impl.PackagingBasedJndiBindingPolicy | 2008-07-01 14:38:01,515 DEBUG [org.jboss.ejb3.proxy.factory.BaseSessionProxyFactory] (main) Binding proxy for UserManagerBean in JNDI at RemoteUserManagerBean So based on your logs, it looks like a deployment ordering issue. anonymous wrote : IMPORTANT: By changing from an @Startup Seam component to a startup servlet I was able to get my .jar and .war to deploy successfully. You mean, no error messages and JBoss boots fine? anonymous wrote : The startup method, servlet.init(), still fails when trying to lookup DBUtilBean With what exception? Same as the previous? Can you post those logs too? Also, if the servlet.init() fails, then the deployment too should fail, which seems to contradict your previous statement. Based on what you have explained so far, this appears to be deployment ordering issue (with Seam?) in 5.0 CR1. I have seen some other user too asking about the deployment ordering based on the contents of application.xml. Let me try out a sample application (without Seam) and see if there are any issues with 5.0 CR1. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165797#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...