Jboss 4.2.2 - deployment of EJB3 MDB causes failure of other EJB 3 deployments
kkkppp May 20, 2013 9:27 AMI have such an MDB:
@MessageDriven(activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType",
propertyValue = "javax.jms.Queue"),
@ActivationConfigProperty(propertyName = "destination",
propertyValue = "queue/RemoveUnusedBlobsQueue") })
@TransactionAttribute(TransactionAttributeType.REQUIRED)
public class RemoveUnusedBlobsBean implements MessageListener {
it deploys fine:
2013-05-20 16:59:05,409 INFO [ejb3.JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=main.ear,jar=SWLargeObjects_ejb3.jar,name=RemoveUnusedBlobsBean,service=EJB3 with dependencies:
2013-05-20 16:59:05,424 INFO [g.jboss.ejb3.EJBContainer] STARTED EJB: com.supportwizard.largeobjects.ejb3.RemoveUnusedBlobsBean ejbName: RemoveUnusedBlobsBean
2013-05-20 16:59:05,424 INFO [g.jboss.ejb3.EJB3Deployer] Deployed: file:/E:/jboss/server/sw/tmp/deploy/tmp2821097761921640693main.ear-contents/SWLargeObjects_ejb3.jar
but next EJB3 jar fails:
2013-05-20 16:59:06,548 INFO [PersistenceUnitDeployment] Starting persistence unit persistence.units:ear=main.ear,jar=homepage_ejb3.jar,unitName=EW
2013-05-20 16:59:06,548 WARN [.system.ServiceController] Problem starting service persistence.units:ear=main.ear,jar=homepage_ejb3.jar,unitName=EW
javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:325)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:216)
If I remove this MDB from deployment (there are other beans in jar so it still deploys), other EJB3 jars deploy without errors.
2013-05-20 17:18:22,544 INFO [ejb3.JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=main.ear,jar=SWLargeObjects_ejb3.jar,name=LargeObjectFacadeBean,service=EJB3 with dependencies:
2013-05-20 17:18:22,544 INFO [ejb3.JmxKernelAbstraction] persistence.units:ear=main.ear,jar=SWLargeObjects_ejb3.jar,unitName=LO
2013-05-20 17:18:22,544 INFO [g.jboss.ejb3.EJBContainer] STARTED EJB: com.supportwizard.largeobjects.ejb3.LargeObjectFacadeBean ejbName: LargeObjectFacadeBean
2013-05-20 17:18:22,560 INFO [g.jboss.ejb3.EJB3Deployer] Deployed: file:/E:/jboss/server/sw/tmp/deploy/tmp8669461113388431680main.ear-contents/SWLargeObjects_ejb3.jar
...
2013-05-20 17:18:24,159 INFO [bernate.util.NamingHelper] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
2013-05-20 17:18:24,159 INFO [ssionFactoryObjectFactory] Bound factory to JNDI name: persistence.units:ear=main.ear,jar=homepage_ejb3.jar,unitName=EW
2013-05-20 17:18:24,159 WARN [ssionFactoryObjectFactory] InitialContext did not implement EventContext
2013-05-20 17:18:24,159 INFO [bernate.util.NamingHelper] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
2013-05-20 17:18:24,160 INFO [ejb3.JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.stateless.StatelessContainer
2013-05-20 17:18:24,160 INFO [ejb3.JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=main.ear,jar=homepage_ejb3.jar,name=DashboardFacade,service=EJB3 with dependencies:
2013-05-20 17:18:24,160 INFO [ejb3.JmxKernelAbstraction] persistence.units:ear=main.ear,jar=homepage_ejb3.jar,unitName=EW
2013-05-20 17:18:24,163 INFO [g.jboss.ejb3.EJBContainer] STARTED EJB: com.supportwizard.homepage.ejb.DashboardFacade ejbName: DashboardFacade
2013-05-20 17:18:24,166 INFO [g.jboss.ejb3.EJB3Deployer] Deployed: file:/E:/jboss/server/sw/tmp/deploy/tmp8669461113388431680main.ear-contents/homepage_ejb3.jar
Any idea what can cause this?