[jboss-jira] [JBoss JIRA] (AS7-5779) Premature access to webapp triggered by blueprint

Thomas Diesler (JIRA) jira-events at lists.jboss.org
Sat Oct 27 15:57:01 EDT 2012


    [ https://issues.jboss.org/browse/AS7-5779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12729610#comment-12729610 ] 

Thomas Diesler commented on AS7-5779:
-------------------------------------

I suppose the client gets hold of the ServletContext via some service. 
What is the contract for that ServletContext service? 
* Is it supposed to be initialized?
* When is it supposed to get registered?
I'd assume the safest option is to init the context when the service gets registered.

??If the issue still exists when we're passing all the CT tests for those I will revisit.??

This is a 'critical' bug scheduled for Alpha1. What is the likelihood that the above will happen in time such that we can resolve this in time too?
                
> Premature access to webapp triggered by blueprint
> -------------------------------------------------
>
>                 Key: AS7-5779
>                 URL: https://issues.jboss.org/browse/AS7-5779
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: OSGi
>            Reporter: Thomas Diesler
>            Assignee: David Bosschaert
>            Priority: Critical
>             Fix For: 7.2.0.Alpha1
>
>         Attachments: org.eclipse.rap.rwt-1.5.1.jar, org.eclipse.rap.rwt.osgi-1.5.1.jar, rwt.simple-1.0.jar
>
>
> {code}
>     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]
> {code}

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


More information about the jboss-jira mailing list