Hi.
I get some exceptions when I try to deploy ear in
JBoss 5.1. Ear works fine in JBoss 4.2.
When I don't change anything JBoss gives following exception:
07:27:29,412 INFO [SessionFactoryObjectFactory] Unbinding factory from JNDI name: persistence.unit:unitName=xxx.ear/entities.jar#EJBXXX
07:27:29,412 INFO [NamingHelper] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
07:27:29,412 INFO [SessionFactoryObjectFactory] Unbound factory from JNDI name: persistence.unit:unitName=xxx.ear/entities.jar#EJBXXX
07:27:29,709 ERROR [AbstractKernelController] Error installing to Real: name=vfszip:/C:/JB501/jboss-5.0.1.GA/server/default/deploy/xxx.ear/ state=PreReal mode=Manual requiredState=Real
org.jboss.deployers.spi.DeploymentException: java.lang.NullPointerException: name cannot be null
at org.jboss.wsf.container.jboss50.deployer.WebServiceDeployerEJB.internalDeploy(WebServiceDeployerEJB.java:100)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1210)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:698)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:290)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NullPointerException: name cannot be null
at javax.management.ObjectName.construct(Unknown Source)
at javax.management.ObjectName.<init>(Unknown Source)
at org.jboss.wsf.container.jboss50.deployer.WebServiceDeployerEJB.internalDeploy(WebServiceDeployerEJB.java:96)
... 26 more
07:27:29,787 WARN [HDScanner] Failed to process changes
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
DEPLOYMENTS IN ERROR:
Deployment "vfszip:/C:/JB501/jboss-5.0.1.GA/server/default/deploy/xxx.ear/" is in error due to the following reason(s): java.lang.NullPointerException: name cannot be null
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:863)
at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:806)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:293)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Exception occurs in the JBoss code where it try to get container name? Where this should be defined?
If I remove all (6) jboss.xml files from projects there is not any exceptions, but then applications try to use wrong jndi names. There is sample of one jboss.xml file.
<?xml version="1.0" encoding="UTF-8"?>
<jboss>
<security-domain>
java:/jaas/xxxSecurity</security-domain>
<enterprise-beans>
<message-driven>
<ejb-name>xxxMessageListener</ejb-name>
<destination-jndi-name>queue/xxxQueue</destination-jndi-name>
</message-driven>
<!-- ======= Creators ======= -->
<session>
<ejb-name>xxxCreator</ejb-name>
<local-jndi-name>ejblocal:com.xx.xx.xx.Creator</local-jndi-name>
</session>
<session>
<ejb-name>yyCreator</ejb-name>
<local-jndi-name>ejblocal:yy.yy.yy.yy.YCreator</local-jndi-name>
</session>
<session>
<ejb-name>bbProcessor</ejb-name>
<local-jndi-name>ejblocal:com.bb.bb.bb.Processor</local-jndi-name>
</session>
</enterprise-beans>
....
....
</jboss>
I also tried to use empty jboss.xml files and same exception occurred.
Ear contains following technologies and its build with eclipse:
-Struts 1.2
-Hibernate
-EJB 3
Please help me someone so we could start to use JBoss 5.1.
Regards
Jaakko