[jboss-osgi-issues] [JBoss JIRA] (JBOSGI-740) HttpService TCK testBundleStopping() failing

[Thomas Diesler (JIRA)]

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

Thomas Diesler updated JBOSGI-740:
----------------------------------

    Comment: was deleted

(was: Won't Fix - OSGi is going to get removed)

    
> HttpService TCK testBundleStopping() failing
> --------------------------------------------
>
>                 Key: JBOSGI-740
>                 URL: https://issues.jboss.org/browse/JBOSGI-740
>             Project: JBoss OSGi
>          Issue Type: Sub-task
>          Components: HttpService, WildFly
>            Reporter: David Bosschaert
>
> The OSGi HTTP Service TCK test testBundleStopping() fails with the following exception:
> {code}org.osgi.framework.BundleException: JBOSGI011254: Cannot start bundle: tb1:4.2.0
> 	at org.jboss.osgi.framework.internal.DefaultBundleLifecycleHandler.start(DefaultBundleLifecycleHandler.java:110)
> 	at org.jboss.as.osgi.service.BundleLifecycleIntegration.start(BundleLifecycleIntegration.java:181)
> 	at org.jboss.osgi.framework.internal.HostBundleState.transitionToActive(HostBundleState.java:292)
> 	at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:228)
> 	at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:522)
> 	at org.jboss.as.osgi.deployment.BundleActivateProcessor$BundleActivateService.start(BundleActivateProcessor.java:127)
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> 	at java.lang.Thread.run(Thread.java:680)
> Caused by: java.lang.LinkageError: loader constraint violation: when resolving interface method "org.osgi.service.http.HttpService.registerServlet(Ljava/lang/String;Ljavax/servlet/Servlet;Ljava/util/Dictionary;Lorg/osgi/service/http/HttpContext;)V" the class loader (instance of org/jboss/osgi/framework/internal/HostBundleClassLoader) of the current class, org/osgi/test/cases/http/tb1/HttpTestBundle2, and the class loader (instance of org/jboss/modules/ModuleClassLoader) for resolved class, org/osgi/service/http/HttpService, have different Class objects for the type javax/servlet/Servlet used in the signature
> 	at org.osgi.test.cases.http.tb1.HttpTestBundle2.start(HttpTestBundle2.java:30)
> 	at org.jboss.osgi.framework.internal.DefaultBundleLifecycleHandler.start(DefaultBundleLifecycleHandler.java:84)
> 	... 10 more{code}
> Seems like a resolution error, it could be related to how the TCK is set up.

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