[jboss-jira] [JBoss JIRA] (AS7-5655) Cannot restart ejb3 bundle after activation failure

Thomas Diesler (JIRA) jira-events at lists.jboss.org
Fri Nov 23 08:21:22 EST 2012


    [ https://issues.jboss.org/browse/AS7-5655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736670#comment-12736670 ] 

Thomas Diesler commented on AS7-5655:
-------------------------------------

I sent a [pull request|https://github.com/jbossas/jboss-as/pull/3502] that restores the test case for that.

It's a general problem with how the Bundle lifecycle maps to the AS deployment model. If start fails we partially undeploy the deployment (i.e. go back through the DUPs until FIRST_MODULE_USE). This keeps the associated module alive. A consecutive restart should progress the deployment through the DUPs again - this does not work for EJB3 deployments.

Many of the DUPs are not designed to repeatedly undeploy/deploy after the module phase. This would be needed to properly support start/stop behaviour of any deployment.  
                
> Cannot restart ejb3 bundle after activation failure
> ---------------------------------------------------
>
>                 Key: AS7-5655
>                 URL: https://issues.jboss.org/browse/AS7-5655
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: EJB, OSGi
>            Reporter: Thomas Diesler
>            Assignee: Bartosz Baranowski
>
> {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


More information about the jboss-jira mailing list