[jboss-jira] [JBoss JIRA] (AS7-2739) Completing Async web request appears to close socket of pipelined request instead of finished request
[
https://issues.jboss.org/browse/AS7-2739?page=com.atlassian.jira.plugin.s...
]
Remy Maucherat commented on AS7-2739:
-------------------------------------
The behavior is mostly correct actually. If data is still available, the connection is
closed because going processing again would be a little more complex. I don't
understand why aggressive pipelining should be used for long running requests where async
is used. If no data is available, OPEN is returned which is the usual HTTP keepalive.
Maybe you should consider using a proxy which supports keepalive.
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/or...
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