[jboss-jira] [JBoss JIRA] (WFLY-8241) EJB deployments with Elytron SD collides in EJB3 SD service

[Jan Kalina (JIRA)]

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

Jan Kalina edited comment on WFLY-8241 at 2/25/17 4:06 AM:
-----------------------------------------------------------

[~fjuma], what was the intention here? Should be be added something to name of service (like deployment name or something) to prevent collisions? Or should be service local somehow?


was (Author: honza889):
[~fjuma], what was the intention here? Should be be added something to name of service (like deployment name or something) to prevent collisions?

> EJB deployments with Elytron SD collides in EJB3 SD service
> -----------------------------------------------------------
>
>                 Key: WFLY-8241
>                 URL: https://issues.jboss.org/browse/WFLY-8241
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB, Security
>            Reporter: Jan Kalina
>            Assignee: Jan Kalina
>            Priority: Critical
>
> Every EJB deployment associated with an Elytron security domain builds *jboss.ejb3.security-domain* service:
> https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jboss/as/ejb3/deployment/processors/EJBDefaultSecurityDomainProcessor.java#L107
> But it fails if there are more such deployments, because it mean second service with the same name:
> {code}
> 00:02:12,118 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.subunit."read-props-limited.ear"."ejb-moduleread-props-limited.jar".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."read-props-limited.ear"."ejb-moduleread-props-limited.jar".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of subdeployment "ejb-moduleread-props-limited.jar" of deployment "read-props-limited.ear"
> 	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 	at java.lang.Thread.run(Thread.java:745)
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.ejb3.security-domain is already registered
> 	at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158)
> 	at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235)
> 	at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768)
> 	at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
> 	at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2555)
> 	at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
> 	at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2555)
> 	at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317)
> 	at org.jboss.as.ejb3.deployment.processors.EJBDefaultSecurityDomainProcessor.deploy(EJBDefaultSecurityDomainProcessor.java:111)
> 	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
> 	... 5 more
> {code}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)