Problem with JBoss 7.2.0-Alpha1-SNAPSHOT
pkilian Oct 18, 2012 2:51 AMFor 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?