[jboss-jira] [JBoss JIRA] Assigned: (AS7-1281) Cannot deploy different EARs with same WARs inside.

[Remy Maucherat (JIRA)]

     [ https://issues.jboss.org/browse/AS7-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Remy Maucherat reassigned AS7-1281:
-----------------------------------

    Assignee: Emanuel Muckenhuber  (was: Remy Maucherat)


Ok, so after reviewing, the service names should probably be based on hostName + pathName. That's what AS 6 was using for the mbean names.

Not using the host breaks vhosting, and the .war deployment name does not have to be unique either (the path where it is mapped must be unique inside a vhost).

> Cannot deploy different EARs with same WARs inside.
> ---------------------------------------------------
>
>                 Key: AS7-1281
>                 URL: https://issues.jboss.org/browse/AS7-1281
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Web
>    Affects Versions: 7.0.0.Final
>         Environment: $uname -a
> Linux 2.6.38-10-generic-pae #46-Ubuntu SMP Tue Jun 28 16:54:49 UTC 2011 i686 i686 i386 GNU/Linux
>            Reporter: Juri Timošin
>            Assignee: Emanuel Muckenhuber
>              Labels: deploy, duplicate-service-exception, ear, ejb, war
>
> Hello, I have a problem of deploying several EARs on jboss-as-7.0.0-Final.
>  
> I have 2 EARs, both have test.war inside them. I cannot deploy both EARs at the same time
>  
> 10:09:31,237 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.subunit."myTest.ear"."test.war".INSTALL: org.jboss.msc.
> service.StartException in service jboss.deployment.subunit."myTest.ear"."test.war".INSTALL: Failed to process phase INSTALL of subdeployment "test.war" of deployment "myTest.ear"
>         at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
>         at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
>         at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
>         at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to add JBoss web deployment service
>         at org.jboss.as.web.deployment.WarDeploymentProcessor.processDeployment(WarDeploymentProcessor.java:234)
>         at org.jboss.as.web.deployment.WarDeploymentProcessor.deploy(WarDeploymentProcessor.java:105)
>         at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
>         ... 5 more
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.web.realm."test.war" is already registered
>         at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154)
>         at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:226)
>         at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:560)
>         at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201)
>         at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2194)
>         at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201)
>         at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2194)
>         at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307)
>         at org.jboss.as.web.deployment.WarDeploymentProcessor.processDeployment(WarDeploymentProcessor.java:209)
>         ... 7 more
>  
> If I deploy them 1 by 1 then only the first one deploys. If i deploy them both at the same time, then both deployments are rolled back.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira