[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=12645088#comment-12645088 ] 

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

Great.

Is this going to be soon, can you say (so I can use the latest build)?
                
> 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