[jboss-jira] [JBoss JIRA] Commented: (JBWEB-205) Invalid async context for servlet: Atmosphere Async Servlet on JBoss Web

Remy Maucherat (JIRA) jira-events at lists.jboss.org
Mon Jul 4 05:53:23 EDT 2011


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

Remy Maucherat commented on JBWEB-205:
--------------------------------------

I was able to run the WAR on the full EE config in the end. Reproducing is not easy and intermittent at best, and I have not been able to identify the cause of the issue. I wanted to compare with what happened when native was installed, but Atmosphere then switches to using the event API rather than Servlet 3, which does not use the same code paths [and I didn't see any problem, but I am not certain since the problem was very intermittent for the other connector].

I am replacing the exception with a log message, since the exception had little benefit and prevented cleanup, while this only appears to be an extra event with no meaning for Servlet 3 async. Beyond that, I have no idea at this time on how to improve this.

> Invalid async context for servlet: Atmosphere Async  Servlet on JBoss Web
> -------------------------------------------------------------------------
>
>                 Key: JBWEB-205
>                 URL: https://issues.jboss.org/browse/JBWEB-205
>             Project: JBoss Web
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Core
>    Affects Versions: JBossWeb-7.0.0.CR1
>         Environment: Firefox 4.0.1 / Chromium 12 
> AS 6.0.0.Final / 6.1.0-SNAPSHOT / AS 7.0.0.CR1 
> Atmosphere 0.7.1/0.7.2 
>            Reporter: Lukáš Fryč
>            Assignee: Remy Maucherat
>            Priority: Critical
>         Attachments: push-jms.war
>
>
> Source of sample for reproduction:
> https://github.com/lfryc/push-jms/commit/9cee160570e049ca4783e1fcbdac25ffef1b10b7
> {code}
> 16:08:28,467 ERROR [org.apache.catalina.connector.CoyoteAdapter] (http-localhost-127.0.0.1-8080-7) An exception or error occurred in the container during the request processing: java.lang.IllegalStateException: Invalid async context for servlet AutoRegisteredPushServlet
> 	at org.apache.catalina.core.StandardWrapperValve.async(StandardWrapperValve.java:643) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1]
> 	at org.apache.catalina.core.StandardWrapperValve.event(StandardWrapperValve.java:402) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1]
> 	at org.apache.catalina.core.StandardContextValve.event(StandardContextValve.java:183) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1]
> 	at org.apache.catalina.valves.ValveBase.event(ValveBase.java:193) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1]
> 	at org.apache.catalina.valves.ValveBase.event(ValveBase.java:193) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1]
> 	at org.apache.catalina.core.StandardHostValve.event(StandardHostValve.java:246) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1]
> 	at org.apache.catalina.valves.ValveBase.event(ValveBase.java:193) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1]
> 	at org.apache.catalina.core.StandardEngineValve.event(StandardEngineValve.java:128) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1]
> 	at org.apache.catalina.connector.CoyoteAdapter.event(CoyoteAdapter.java:265) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1]
> 	at org.apache.coyote.http11.Http11Processor.event(Http11Processor.java:757) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1]
> 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.event(Http11Protocol.java:615) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1]
> 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:938) [jbossweb-7.0.0.CR4.jar:7.0.0.CR1]
> 	at java.lang.Thread.run(Thread.java:636) [:1.6.0_20]
> {code}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       



More information about the jboss-jira mailing list