anonymous wrote : 2008-07-15 11:20:36,582 INFO [org.jboss.ejb3.MCKernelAbstraction] installing bean: jboss.j2ee:ear=1 | 0.mpee.local.20080714.1755.ear,jar=mpee.jar,name=ServiceManagerBeanImpl,service=EJB3 with dependencies: | 2008-07-15 11:20:36,582 INFO [org.jboss.ejb3.MCKernelAbstraction] and demands: | 2008-07-15 11:20:36,582 INFO [org.jboss.ejb3.MCKernelAbstraction] jboss.ejb:service=EJBTimerSe | rvice | 2008-07-15 11:20:36,582 INFO [org.jboss.ejb3.MCKernelAbstraction] and supplies: | 2008-07-15 11:20:36,582 INFO [org.jboss.ejb3.MCKernelAbstraction] Class:com.telrock.mpee.busin | ess.ServiceManagerBean$IRemote | 2008-07-15 11:20:36,582 INFO [org.jboss.ejb3.MCKernelAbstraction] Class:com.telrock.mpee.busin | ess.ServiceManagerBean$ILocal | 2008-07-15 11:20:36,584 DEBUG [org.jboss.ejb3.Ejb3Deployment] Bound ejb3 container jboss.j2ee:ear=10 | .mpee.local.20080714.1755.ear,jar=mpee.jar,name=ServiceManagerBeanImpl,service=EJB3 These log messages actually don't mean that the bean (interfaces) have been bound to the JNDI. This is the just the parsing step. The actual binding happens later on. Unfortunately, the jndi bindings logs are at DEBUG level and don't appear on the console. Here's an example logs from my deployment which has an EJB3 with the @RemoteBinding annotation. The actual jndi-binding logs appear after you see the STARTED ejb log in server.log: | 2008-07-15 17:58:53,536 INFO [org.jboss.ejb3.EJBContainer] (main) STARTED EJB: org.myapp.ejb.impl.UserManagerBean ejbName: UserManagerBean | 2008-07-15 17:58:53,536 DEBUG [org.jboss.ejb3.proxy.factory.ProxyFactoryHelper] (main) Obtaining JNDI name from policy org.jboss.ejb3.jndipolicy.impl.PackagingBasedJndiBindingPolicy | 2008-07-15 17:58:53,536 DEBUG [org.jboss.ejb3.proxy.factory.ProxyFactoryHelper] (main) Obtaining JNDI name from policy org.jboss.ejb3.jndipolicy.impl.PackagingBasedJndiBindingPolicy | 2008-07-15 17:58:53,536 DEBUG [org.jboss.ejb3.proxy.factory.BaseSessionProxyFactory] (main) Binding proxy for UserManagerBean in JNDI at RemoteUserManagerBean | anonymous wrote : Basically, what we have is a ContextListener in the war that calls the ServiceManager EJB as the application is deployed. Looks like a deployment ordering issue. Can you try this: - Stop the server - Remove your WAR from the deploy folder and let the EJB jar/ear be present in the deploy folder. - Start the server - Once the server is completely started (i.e. the EJBs deployed), place the WAR in the deploy folder so that the WAR is picked up for hot deployment. See if that works. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164482#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...