[jboss-jira] [JBoss JIRA] (AS7-2739) Completing Async web request appears to close socket of pipelined request instead of finished request

[David White (Commented) (JIRA)]

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

David White commented on AS7-2739:
----------------------------------

2 more things:

"I don't understand why aggressive pipelining should be used for long running requests where async is used" - I understand that you are justifying closing the request instead of the more complex pipeline processing. I'm not pipelining but wonder if the latest Tomcat code works better here (I don't like the fact that the Jboss code is so different). I can forsee cases where pipelined requests would be async but this is theoretical for now.

"consider using a proxy which supports keepalive" - in nginx you can turn off proxy buffering and it will synchronously connect the upstream to the client (so the client gets the data immediately), but this is a resource issue which is why it is off by default. It's also a (very slight) waste of Jboss socket resource.

                
> Completing Async web request appears to close socket of pipelined request instead of finished request
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AS7-2739
>                 URL: https://issues.jboss.org/browse/AS7-2739
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Web
>    Affects Versions: 7.1.0.Alpha1
>         Environment: linux centos 64bit
> sun JDK 1.6
>            Reporter: David White
>            Assignee: Remy Maucherat
>
> Servlet 3.0 page call AsyncContext.complete() sometime after startAsync()
> The web request has no more input.
> The socket connection should be closed if KeepAlive is false, but it remains open for 60 more seconds.
> Code debugging indicates a bug on line 802 of org.apache.coyote.http11.Http11AprProcessor.java
> http://anonsvn.jboss.org/repos/jbossweb/tags/JBOSSWEB_7_0_3_FINAL/java/org/apache/coyote/http11/Http11AprProcessor.java
> It returns the socket close flag for unfinished requests instead of finished requests.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira