[jboss-jira] [JBoss JIRA] (AS7-5114) JACC EJB permissions are not deployed

[Stuart Douglas (JIRA)]

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

Stuart Douglas moved JBPAPP-9443 to AS7-5114:
---------------------------------------------

              Project: Application Server 7  (was: JBoss Enterprise Application Platform)
                  Key: AS7-5114  (was: JBPAPP-9443)
             Workflow: GIT Pull Request workflow   (was: jira)
    Affects Version/s: 7.1.2.Final (EAP)
                           (was: EAP 6.0.0 (CR1))
          Component/s: Security
                           (was: Security)
             Security:     (was: JBoss Internal)
       Docs QE Status:   (was: NEW)

    
> JACC EJB permissions are not deployed
> -------------------------------------
>
>                 Key: AS7-5114
>                 URL: https://issues.jboss.org/browse/AS7-5114
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Security
>    Affects Versions: 7.1.2.Final (EAP)
>            Reporter: Josef Cacek
>            Assignee: Anil Saldhana
>            Priority: Critical
>
> It seems, there is a problem with DeploymentUnitProcessor ordering in AS, which causes JACC permissions are not created for EJBs. The JaccEjbDeploymentProcessor (uses JACC permissions) runs before the EEModuleConfigurationProcessor (creates JACC permissions - calling EjbJaccConfigurator.configure()).
> Both processors are registered to INSTALL phase:
> {noformat}
> ./ejb3/src/main/java/org/jboss/as/ejb3/subsystem/EJB3SubsystemAdd.java:207:                processorTarget.addDeploymentProcessor(EJB3Extension.SUBSYSTEM_NAME, Phase.INSTALL, Phase.INSTALL_EJB_JACC_PROCESSING, new JaccEjbDeploymentProcessor());
> {noformat}
> {noformat}
> ./ee/src/main/java/org/jboss/as/ee/subsystem/EeSubsystemAdd.java:181:                processorTarget.addDeploymentProcessor(EeExtension.SUBSYSTEM_NAME, Phase.INSTALL, Phase.INSTALL_EE_MODULE_CONFIG, new EEModuleConfigurationProcessor());
> {noformat}
> and stacktraces with usage:
> {panel}
> Thread [MSC service thread 1-1] (Suspended (breakpoint at line 44 in EjbSecurityDeployer))	
> 	EjbSecurityDeployer.getMetaDataType() line: 44	
> 	EjbSecurityDeployer(AbstractSecurityDeployer<T>).deploy(DeploymentUnit) line: 38	
> 	JaccEjbDeploymentProcessor.deploy(DeploymentPhaseContext) line: 54	
> 	DeploymentUnitPhaseService<T>.start(StartContext) line: 116	
> 	ServiceControllerImpl$StartTask.startService(Service<? extends S>, StartContext) line: 1811	
> 	ServiceControllerImpl$StartTask.run() line: 1746	
> 	ThreadPoolExecutor$Worker.runTask(Runnable) line: 886	
> 	ThreadPoolExecutor$Worker.run() line: 908	
> 	ServiceContainerImpl$ServiceThread(Thread).run() line: 662	
> Thread [MSC service thread 1-1] (Suspended (breakpoint at line 40 in EjbJaccConfigurator))	
> 	EjbJaccConfigurator.configure(DeploymentPhaseContext, ComponentDescription, ComponentConfiguration) line: 40	
> 	EEModuleConfigurationProcessor.deploy(DeploymentPhaseContext) line: 83	
> 	DeploymentUnitPhaseService<T>.start(StartContext) line: 116	
> 	ServiceControllerImpl$StartTask.startService(Service<? extends S>, StartContext) line: 1811	
> 	ServiceControllerImpl$StartTask.run() line: 1746	
> 	ThreadPoolExecutor$Worker.runTask(Runnable) line: 886	
> 	ThreadPoolExecutor$Worker.run() line: 908	
> 	ServiceContainerImpl$ServiceThread(Thread).run() line: 662	
> {panel}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira