[jboss-jira] [JBoss JIRA] (AS7-4252) Same persistence unit names in unrelated deployments cause service name collision, prevents deployment ("Service jboss.naming.context.java.myEMF is already registered")
Scott Marlow (JIRA)
jira-events at lists.jboss.org
Thu Mar 22 09:35:47 EDT 2012
[ https://issues.jboss.org/browse/AS7-4252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678647#comment-12678647 ]
Scott Marlow commented on AS7-4252:
-----------------------------------
This scared me at first, since each pu name should be fully qualified by the deployment name (making it unique).
I think that you set pu property "jboss.entity.manager.factory.jndi.name=myEMF", in both applications. Try making that a unique name instead.
> Same persistence unit names in unrelated deployments cause service name collision, prevents deployment ("Service jboss.naming.context.java.myEMF is already registered")
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-4252
> URL: https://issues.jboss.org/browse/AS7-4252
> Project: Application Server 7
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 7.1.1.Final
> Reporter: Ondrej Zizka
> Assignee: Scott Marlow
>
> STR: Deploy both wicket quickstarts from here:
> https://github.com/OndraZizka/quickstart/tree/QS-wicket
> {code}
> 11:03:13,184 INFO [org.jboss.as.repository] (management-handler-thread - 11) JBAS014900: Content added at location /home/ondra/work/AS7/ozizka-git2/build/target/jboss-as-7.1.1.Final-redhat-1/standalone/data/content/d7/ef102ffa0086dd1ed05a85c063618f1ddab907/content
> 11:03:13,300 INFO [org.jboss.as.server.deployment] (MSC service thread 1-15) JBAS015876: Starting deployment of "as7-quickstart-wicket-war.war"
> 11:03:15,144 INFO [org.jboss.as.jpa] (MSC service thread 1-15) JBAS011401: Read persistence.xml for defaultPersistenceUnit
> 11:03:15,213 INFO [org.jboss.weld.deployer] (MSC service thread 1-12) JBAS016002: Processing weld deployment as7-quickstart-wicket-war.war
> 11:03:15,326 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-12) JNDI bindings for session bean named ContactDaoBean in deployment unit deployment "as7-quickstart-wicket-war.war" are as follows:
> java:global/as7-quickstart-wicket-war/ContactDaoBean!org.jboss.as.quickstarts.wicket.war.dao.ContactDaoLocal
> java:app/as7-quickstart-wicket-war/ContactDaoBean!org.jboss.as.quickstarts.wicket.war.dao.ContactDaoLocal
> java:module/ContactDaoBean!org.jboss.as.quickstarts.wicket.war.dao.ContactDaoLocal
> java:global/as7-quickstart-wicket-war/ContactDaoBean
> java:app/as7-quickstart-wicket-war/ContactDaoBean
> java:module/ContactDaoBean
> 11:03:15,566 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-14) MSC00001: Failed to start service jboss.deployment.unit."as7-quickstart-wicket-war.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."as7-quickstart-wicket-war.war".INSTALL: Failed to process phase INSTALL of deployment "as7-quickstart-wicket-war.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final-redhat-1.jar:7.1.1.Final-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011446: Failed to add persistence unit service for defaultPersistenceUnit
> at org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor.deployPersistenceUnit(PersistenceUnitDeploymentProcessor.java:383)
> at org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor.addPuService(PersistenceUnitDeploymentProcessor.java:258)
> at org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor.handleWarDeployment(PersistenceUnitDeploymentProcessor.java:194)
> at org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor.deploy(PersistenceUnitDeploymentProcessor.java:118)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final-redhat-1.jar:7.1.1.Final-redhat-1]
> ... 5 more
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.naming.context.java.myEMF is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:227) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:560) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2228) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2228) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor.deployPersistenceUnit(PersistenceUnitDeploymentProcessor.java:358)
> ... 9 more
> 11:03:15,835 INFO [org.jboss.as.server] (management-handler-thread - 11) JBAS015870: Deploy of deployment "as7-quickstart-wicket-war.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"as7-quickstart-wicket-war.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"as7-quickstart-wicket-war.war\".INSTALL: Failed to process phase INSTALL of deployment \"as7-quickstart-wicket-war.war\""}}
> 11:03:15,861 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment as7-quickstart-wicket-war.war in 26ms
> 11:03:15,863 INFO [org.jboss.as.controller] (management-handler-thread - 11) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.deployment.unit."as7-quickstart-wicket-war.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."as7-quickstart-wicket-war.war".INSTALL: Failed to process phase INSTALL of deployment "as7-quickstart-wicket-war.war"
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list