[jboss-osgi-issues] [JBoss JIRA] (JBOSGI-674) Cannot restart ejb3 bundle after activation failure

[Thomas Diesler (JIRA)]

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

Thomas Diesler updated JBOSGI-674:
----------------------------------

    Fix Version/s: Awaiting WildFly Support

    
> Cannot restart ejb3 bundle after activation failure
> ---------------------------------------------------
>
>                 Key: JBOSGI-674
>                 URL: https://issues.jboss.org/browse/JBOSGI-674
>             Project: JBoss OSGi
>          Issue Type: Bug
>          Components: Enterprise OSGi, WildFly
>            Reporter: Thomas Diesler
>             Fix For: Awaiting WildFly Support
>
>
> {code}
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011030: Could not configure component SampleSFSB
> 	at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:91)
> 	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> 	... 5 more
> Caused by: java.lang.IllegalArgumentException: JBAS011085: Can't add org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor$Factory at 6f9e0e7b, priority 0x500 is already taken by org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor$Factory at 6f9e0e7b
> 	at org.jboss.as.ee.component.interceptors.OrderedItemContainer.add(OrderedItemContainer.java:58)
> 	at org.jboss.as.ee.component.ComponentConfiguration.addComponentInterceptor(ComponentConfiguration.java:181)
> 	at org.jboss.as.ejb3.component.stateful.StatefulComponentDescription$2.configure(StatefulComponentDescription.java:153)
> 	at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:80)
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira