[jboss-jira] [JBoss JIRA] (AS7-4653) LoggingConfigurationProcessor incorrectly assumes attached module

[James Perkins (JIRA)]

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

James Perkins reopened AS7-4653:
--------------------------------



Read it wrong, the PR was not merged.
                
> LoggingConfigurationProcessor incorrectly assumes attached module
> -----------------------------------------------------------------
>
>                 Key: AS7-4653
>                 URL: https://issues.jboss.org/browse/AS7-4653
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Logging
>            Reporter: Thomas Diesler
>            Assignee: James Perkins
>             Fix For: 7.1.2.Final-redhat1
>
>
> OSGi bundle deployments may not have a module attached. They get their module when they reach RESOLVED state, which is not part of DUP processing.
> {code}
> 10:00:43,264 ERROR [org.jboss.as.server.deployment] JBAS015892: Deployment unit processor org.jboss.as.logging.LoggingConfigurationProcessor at 2ce628d8 unexpectedly threw an exception during undeploy phase POST_MODULE of deployment "org.apache.aries.blueprint:org.apache.aries.blueprint:0.4": java.lang.NullPointerException
> 	at org.jboss.as.logging.LoggingConfigurationProcessor.undeploy(LoggingConfigurationProcessor.java:120)
> 	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.safeUndeploy(DeploymentUnitPhaseService.java:168) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> 	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.stop(DeploymentUnitPhaseService.java:162) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> {code}

--
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