[jboss-jira] [JBoss JIRA] (WFLY-1390) Undertow: javamelody SessionListener stop working

[Stuart Douglas (JIRA)]

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

Stuart Douglas resolved WFLY-1390.
----------------------------------

    Resolution: Out of Date


Wildly no longer contains OSGI support in the core distribution.
                
> Undertow: javamelody SessionListener stop working
> -------------------------------------------------
>
>                 Key: WFLY-1390
>                 URL: https://issues.jboss.org/browse/WFLY-1390
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (Undertow)
>    Affects Versions: 8.0.0.Alpha2
>            Reporter: Igor Shulika
>            Assignee: Stuart Douglas
>         Attachments: jaffa-3rd-party-javamelody-core-1.43.0.jar, jaffa-sample-webapp-6.0.jar
>
>
> I'm deploying JavaMelody OSGi bundle on the latest WildFly 8.0.0.Alpha2-SNAPSHOT server. Since I switch from Jbossweb to Undertow the JavaMelody SessionListener stop working.
> Please see below configuration in the web.xml file.
>   <listener>
>     <listener-class>net.bull.javamelody.SessionListener</listener-class>
>   </listener>
> Please see error trace below.
> Note: It works in Jbossweb.
> Thanks!
> 09:51:44,005 INFO  [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001: Bundle installed: org.test.sample.webapp.my-sample-webapp:6.0.0
> 09:52:15,221 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-10) MSC000001: Failed to start service jboss.deployment.unit."my-sample-webapp-6.0.jar".Activate: org.jboss.msc.service.StartException in service jboss.deployment.unit."my-sample-webapp-6.0.jar".Activate: Failed to start service
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1930) [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_21]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
> 	at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
> Caused by: org.jboss.osgi.deployment.interceptor.LifecycleInterceptorException: JBAS017345: Timeout context service activation: service jboss.undertow.deployment.default-host./test
> 	at org.jboss.as.osgi.web.WebContextLifecycleInterceptor.invoke(WebContextLifecycleInterceptor.java:105)
> 	at org.jboss.osgi.deployment.interceptor.AbstractLifecycleInterceptorService.handleStateChange(AbstractLifecycleInterceptorService.java:264)
> 	at org.jboss.osgi.framework.internal.AbstractBundleState.changeState(AbstractBundleState.java:253)
> 	at org.jboss.osgi.framework.internal.AbstractBundleState.changeState(AbstractBundleState.java:242)
> 	at org.jboss.osgi.framework.internal.UserBundleState.startInternalNow(UserBundleState.java:637)
> 	at org.jboss.osgi.framework.internal.UserBundleState.startInternal(UserBundleState.java:526)
> 	at org.jboss.osgi.framework.internal.BundleManagerPlugin.startBundle(BundleManagerPlugin.java:560)
> 	at org.jboss.as.osgi.deployment.BundleActivateProcessor$BundleActivateService.start(BundleActivateProcessor.java:125)
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1974) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1907) [jboss-msc-1.1.2.Final.jar:1.1.2.Final]
> 	... 3 more
> Caused by: java.util.concurrent.TimeoutException: JBAS017345: Timeout context service activation: service jboss.undertow.deployment.default-host./jaffa
> 	at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$ContextActivatorImpl.start(UndertowDeploymentService.java:158)
> 	at org.jboss.as.osgi.web.WebContextLifecycleInterceptor.invoke(WebContextLifecycleInterceptor.java:100)
> 	... 12 more

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