Problem with JBoss 7.2.0-Alpha1-SNAPSHOT

[pkilian]

For our OSGi based Web-Application we use the RWT Widget Toolkit from the Eclipse RAP project.

With JBoss 7.2.0-Alpha1-SNAPSHOT following exception is thrown:

11:27:58,696 ERROR [org.eclipse.rap.rwt.osgi] (Thread-67) Unable to start RWT application.: java.lang.IllegalStateException: ServletConfig has not been initialized

          at javax.servlet.GenericServlet.getServletContext(GenericServlet.java:197)

          at org.eclipse.rap.rwt.osgi.internal.ApplicationReferenceImpl.createApplication(ApplicationReferenceImpl.java:71)

          at org.eclipse.rap.rwt.osgi.internal.ApplicationReferenceImpl.start(ApplicationReferenceImpl.java:61)

          at org.eclipse.rap.rwt.osgi.internal.ApplicationLauncherImpl.doLaunch(ApplicationLauncherImpl.java:103)

          at org.eclipse.rap.rwt.osgi.internal.ApplicationLauncherImpl.launch(ApplicationLauncherImpl.java:85)

          at org.eclipse.rap.rwt.osgi.internal.ApplicationLauncherImpl.launch(ApplicationLauncherImpl.java:162)

          at org.eclipse.rap.rwt.osgi.internal.ApplicationLauncherImpl.launchWithConfiguration(ApplicationLauncherImpl.java:149)

          at org.eclipse.rap.rwt.osgi.internal.ApplicationLauncherImpl.addConfiguration(ApplicationLauncherImpl.java:64)

          at org.eclipse.rap.rwt.osgi.internal.ApplicationConfigurationTracker.addingService(ApplicationConfigurationTracker.java:35)

          at org.eclipse.rap.rwt.osgi.internal.ApplicationConfigurationTracker.addingService(ApplicationConfigurationTracker.java:1)

          at org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:896) [jbosgi-resolver-api-3.0.0.CR8.jar:3.0.0.CR8]

          at org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:261) [jbosgi-resolver-api-3.0.0.CR8.jar:3.0.0.CR8]

          at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:233) [jbosgi-resolver-api-3.0.0.CR8.jar:3.0.0.CR8]

          at org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:840) [jbosgi-resolver-api-3.0.0.CR8.jar:3.0.0.CR8]

          at org.jboss.osgi.framework.internal.FrameworkEventsPlugin.fireServiceEvent(FrameworkEventsPlugin.java:525) [jbosgi-framework-core-2.0.0.CR36.jar:2.0.0.CR36]

          at org.jboss.osgi.framework.internal.ServiceManagerPlugin.registerService(ServiceManagerPlugin.java:162) [jbosgi-framework-core-2.0.0.CR36.jar:2.0.0.CR36]

          at org.jboss.osgi.framework.internal.AbstractBundleContext.registerService(AbstractBundleContext.java:305) [jbosgi-framework-core-2.0.0.CR36.jar:2.0.0.CR36]

          at org.apache.aries.blueprint.container.BlueprintContainerImpl.registerService(BlueprintContainerImpl.java:394)

          at org.apache.aries.blueprint.container.ServiceRecipe.register(ServiceRecipe.java:188)

          at org.apache.aries.blueprint.container.BlueprintContainerImpl.registerServices(BlueprintContainerImpl.java:652)

          at org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:325)

          at org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:228)

          at org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:48)

          at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [rt.jar:1.6.0_24]

          at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_24]

          at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_24]

          at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) [rt.jar:1.6.0_24]

          at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206) [rt.jar:1.6.0_24]

          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_24]

          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_24]

          at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_24]

Few lines before the HttpService ist registered:

1:27:58,695 INFO  [org.jboss.as.osgi] (Blueprint Extender: 2) JBAS011913: Register HttpService alias: /servlet_context_finder

Maybe the servlet is not initialized?

[thomas.diesler]

Ok, we are trying to get to the bottom of this.

https://issues.jboss.org/browse/AS7-5779

[bosschaert]

Hi Peter,

getServletContext() should only really be called once Servlet.init() is called. How are you getting hold of your Servlet instance?

Thanks,

David

[pkilian]

Hi David,

sorry, but this is handled in the RWT code, so I am not able to give you an answer :-(

We only register a service, then RWT does the wiring with the HttpService

This approach is explained in http://eclipsesource.com/blogs/2011/08/29/lightweight-osgi-applications-using-raps-widget-toolkit/ and more in deep here http://www.codeaffine.com/2011/08/26/raprwt-osgi-integration/

Tanks

Peter

[bosschaert]

Hi Peter,

In that case would you be able to attach a test case to https://issues.jboss.org/browse/AS7-5779 that exposes the issue? That would help me reproducing it and figuring out what might be going wrong. I could try to cobble together what you're using from those 2 blogs but it would be more efficient if you could simply attach the bundles needed to expose the issue to the bug.

Thanks,

David

[pkilian]

I created a bundle of the example from https://github.com/ralfstx/rap-helpers/tree/master/example.rwt.simple and attached it with the RWT bundles.

To reproduce this Issue start your JBoss and copy the Jars in the following order to the deploy folder:

1.) org.eclipse.rap.rwt-1.5.1.jar

2.) org.eclipse.rap.rwt.osgi-1.5.1.jar

3.) rwt.simple-1.0.jar

I waited between the copy operations until the bundle is coplete deployed.

[bosschaert]

Hi Peter, you probably also deployed Blueprint? I see that it's from Aries. Which version?

[pkilian]

Hi David,

here is my Blueprint configuration:

                <capability name="org.apache.aries:org.apache.aries.util:0.4" startlevel="1"/>

                <capability name="org.apache.aries.proxy:org.apache.aries.proxy:0.4" startlevel="1"/>

                <capability name="org.apache.aries.blueprint:org.apache.aries.blueprint:0.4" startlevel="1"/>

[bosschaert]

Thanks Peter. I have been able to reproduce your problem. Will look at it in more detail soon.

[pkilian]

Thank you David.