[jboss-jira] [JBoss JIRA] (WFLY-1361) WeldListener throws JBAS016071: Singleton not set for ModuleClassLoader during application undeployment

[Stuart Douglas (JIRA)]

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

Stuart Douglas resolved WFLY-1361.
----------------------------------

    Fix Version/s: 8.0.0.Alpha2
       Resolution: Done

    
> WeldListener throws JBAS016071: Singleton not set for ModuleClassLoader during application undeployment
> -------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-1361
>                 URL: https://issues.jboss.org/browse/WFLY-1361
>             Project: WildFly
>          Issue Type: Bug
>          Components: CDI / Weld
>            Reporter: jaikiran pai
>            Assignee: Stuart Douglas
>             Fix For: 8.0.0.Alpha2
>
>
> Testing some of the quickstarts against WildFly upstream, I see this exception during application undeployment for many application:
> {code}
> 14:58:56,111 WARN  [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000004: Failure during stop of service jboss.undertow.deployment.default-host./jboss-as-ejb-throws-exception-web: java.lang.IllegalStateException: JBAS016071: Singleton not set for ModuleClassLoader for Module "org.wildfly.extension.undertow:main" from local module loader @294944 (finder: local module finder @8923f5 (roots: /jbossas/as7/wildfly/build/target/wildfly-8.0.0.Alpha1-SNAPSHOT/modules,/jbossas/as7/wildfly/build/target/wildfly-8.0.0.Alpha1-SNAPSHOT/modules/system/layers/base)). This means that you are trying to access a weld deployment with a Thread Context ClassLoader that is not associated with the deployment.
> 	at org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:75)
> 	at org.jboss.weld.Container.instance(Container.java:54)
> 	at org.jboss.weld.context.http.HttpSessionContextImpl.getConversationContext(HttpSessionContextImpl.java:63)
> 	at org.jboss.weld.context.http.HttpSessionContextImpl.destroy(HttpSessionContextImpl.java:39)
> 	at org.jboss.weld.servlet.WeldListener.sessionDestroyed(WeldListener.java:128)
> 	at io.undertow.servlet.core.ApplicationListeners.sessionDestroyed(ApplicationListeners.java:215)
> 	at io.undertow.servlet.core.SessionListenerBridge.sessionDestroyed(SessionListenerBridge.java:38)
> 	at io.undertow.server.session.SessionListeners.sessionDestroyed(SessionListeners.java:38)
> 	at io.undertow.server.session.InMemorySessionManager.stop(InMemorySessionManager.java:61)
> 	at io.undertow.servlet.core.DeploymentManagerImpl.stop(DeploymentManagerImpl.java:659)
> 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.stop(UndertowDeploymentService.java:90)
> 	at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2082) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
> 	at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2043) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_15]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_15]
> 	at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_15]
> {code}
> I haven't yet investigated what the problem is. It doesn't seem to be causing any problems except for this log. An example quickstart to test is here https://github.com/jaikiran/quickstart/tree/wildfly-upgrade/greeter (start the server, deploy that app and then stop the server to see that exception log)

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