... and my frustration is growing... I restarted the server and then experienced another error: anonymous wrote : --- MBeans waiting for other MBeans --- | ObjectName: jboss.j2ee:module=concept.jar,uid=31374579,service=EJB3 | State: FAILED | Reason: java.lang.RuntimeException: javax.management.InstanceAlreadyExistsException: jboss.j2ee:jar=concept.jar,name=EntityServiceBean,service=EJB3 already registered. | | --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- | ObjectName: jboss.j2ee:module=concept.jar,uid=31374579,service=EJB3 | State: FAILED | Reason: java.lang.RuntimeException: javax.management.InstanceAlreadyExistsException: jboss.j2ee:jar=concept.jar,name=EntityServiceBean,service=EJB3 already registered. It seems that the service is installed when deploying my sar which is not reacting to its own dependencies (the original issue). My service xml file: <?xml version="1.0" encoding="UTF-8"?> | | <server> | <mbean code="concept.jmx.Checker" name="concept:jmx=concept.jmx.Checker"> | </mbean> | <depends-list> | <depends> | jboss.j2ee:jar=concept.jar,name=EntityServiceBean,service=EJB3 | </depends> | <depends>persistence.units:unitName=concept</depends> | </depends-list> | </server> Can anyone come with a suggestion of how o solve this? Do I need to make my deployer sleep between deploying my jar and sar, to be sure that the jar is installed when the sar file is deployed? This is an ugly solution and I am open for other suggestions. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974489#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...