Have you put a dependency on the EJBDeployer within your @Service? Try something like @Service (objectName="trail:service=calculator") @Management(Calculator.class) @Depends( "jboss.ejb3:service=EJB3Deployer" ) public class CalculatorMBean implements Calculator { @Ejb TheBean myBean; that way the EJBDeployer has a chance to init and start before your service does thereby ensuring that the EJB is around. I wonder can you put a depends directly on the EJB itself. That would be the best I would think. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4017145#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...