[jboss-jira] [JBoss JIRA] (WFLY-11903) Deployment failure if existing HA deployment contains a common EJB class

[Brad Maxwell (Jira)]

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

Brad Maxwell reassigned WFLY-11903:
-----------------------------------

    Assignee: JBoss SET  (was: Paul Ferraro)


> Deployment failure if existing HA deployment contains a common EJB class
> ------------------------------------------------------------------------
>
>                 Key: WFLY-11903
>                 URL: https://issues.jboss.org/browse/WFLY-11903
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering
>            Reporter: Brad Maxwell
>            Assignee: JBoss SET
>            Priority: Major
>             Fix For: 7.2.2.GA
>
>
> Currently, the command dispatcher ID uses the bean name.  This needs to be qualified using the deployment name.
> {noformat}Thrown in org.wildfly.clustering.server.dispatcher.MangedCommandDispatcherFactory.cre>ateCommandDispatcher(Object id, C context) line 98 "jboss.deployment.subunit.\"app2.ear\".\"app2.war\".component.StatefullBean.START" => "java.lang.Ille galArgumentException: WFLYCLSV0017: A command dispatcher for StatefullBean already exists, but with a different command context slave1 | [Server:group1] Caused by: java.lang.IllegalArgumentException: WFLYCLSV0017: A command dispatcher for StatefullBean alrea dy exists, but with a different command context",
> slave1 | [Server:group1] "jboss.deployment.subunit.\"app2.ear\".\"app2.war\".component.StatefulBean2.START" => "java.lang.IllegalA rgumentException: WFLYCLSV0017: A command dispatcher for StatefulBean2 already exists, but with a different command context slave1 | [Server:group1] Caused by: java.lang.IllegalArgumentException: WFLYCLSV0017: A command dispatcher for StatefulBean2 already e xists, but with a different command context"
> slave1 | [Server:group1] },
> slave1 | [Server:group1] "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
> slave1 | [Server:group1] "Services that were unable to start:" => [ slave1 | [Server:group1] "jboss.deployment.subunit.\"app2.ear\".\"app2.war\".moduleDeploymentRuntimeInformationStart", slave1 | [Server:group1] "jboss.deployment.unit.\"app2.ear\".WeldEndInitService", slave1 | [Server:group1] "jboss.undertow.deployment.default-server.default-host./app2"
> slave1 | [Server:group1] ], slave1 | [Server:group1] "Services that may be the cause:" => `
> {noformat}



--
This message was sent by Atlassian Jira
(v7.12.1#712002)