[ https://issues.jboss.org/browse/AS7-2780?page=com.atlassian.jira.plugin.s... ] David White commented on AS7-2780: ---------------------------------- Remy claims correct operation (see original) but the processing could be more efficient. Or at least put some helpful comments in the code to avoid the confused statements in AS7-2739. -- 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

[ https://issues.jboss.org/browse/AS7-2780?page=com.atlassian.jira.plugin.s... ] David White updated AS7-2780: ----------------------------- Description: Completing Async pipelined web request closes socket connection Apparently a new socket connection will be used to continue processing was: 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/or... It returns the socket close flag for unfinished requests instead of finished requests. Forum Reference: http://community.jboss.org/thread/175220 (was: http://community.jboss.org/thread/175220) Sorry Remy, this was not meant to be a duplicate. I'm splitting off the pipelined issue from the keepalive issue (note subject changes) But I wont re-open it as it's the keepalive issue that I want fixed. -- 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