[JBoss JIRA] (AS7-2739) Completing Async web request appears to close socket of pipelined request instead of finished request
2:45 p.m.
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
2:22 a.m.
[
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
4:05 a.m.
[
https://issues.jboss.org/browse/AS7-2739?page=com.atlassian.jira.plugin.s...
]
David White commented on AS7-2739:
----------------------------------
I see.
The bug then is a lack of any keepalive processing on close async requests.
Nginx, like many other proxies, talks http1.0 to the upstream, and for good measure adds a
"Connection:close" header (so should still work with only http1.1 upstreams).
I'll take another look to see how keepalive works for non-async requests.
P.S. Why is the code so different from Tomcat 7.0.22, that does not have this bug?
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
4:23 a.m.
[
https://issues.jboss.org/browse/AS7-2739?page=com.atlassian.jira.plugin.s...
]
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/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
4:40 a.m.
[
https://issues.jboss.org/browse/AS7-2739?page=com.atlassian.jira.plugin.s...
]
Remy Maucherat commented on AS7-2739:
-------------------------------------
There's a keepalive flag that is going to be used to close the socket if needed in
event mode as well.
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
4:59 a.m.
[
https://issues.jboss.org/browse/AS7-2739?page=com.atlassian.jira.plugin.s...
]
David White updated AS7-2739:
-----------------------------
Forum Reference: http://community.jboss.org/thread/175220
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
5:51 a.m.
[
https://issues.jboss.org/browse/AS7-2739?page=com.atlassian.jira.plugin.s...
]
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/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
9:11 a.m.
New subject: [JBoss JIRA] (AS7-2739) Completing Async web request does not respect keepAlive flag
[
https://issues.jboss.org/browse/AS7-2739?page=com.atlassian.jira.plugin.s...
]
David White updated AS7-2739:
-----------------------------
Summary: Completing Async web request does not respect keepAlive flag (was:
Completing Async web request appears to close socket of pipelined request instead of
finished request)
Forum Reference: http://community.jboss.org/thread/175220 (was:
http://community.jboss.org/thread/175220)
Completing Async web request does not respect keepAlive flag
------------------------------------------------------------
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
2:28 p.m.
New subject: [JBoss JIRA] (AS7-2739) Completing Async web request does not respect keepAlive flag
[
https://issues.jboss.org/browse/AS7-2739?page=com.atlassian.jira.plugin.s...
]
Remy Maucherat resolved AS7-2739.
---------------------------------
Fix Version/s: 7.1.0.CR1
Resolution: Done
This should now be integrated.
Completing Async web request does not respect keepAlive flag
------------------------------------------------------------
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
Fix For: 7.1.0.CR1
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
4793
days inactive
4799
days old
8 comments
5 participants
participants (5)
-
David White (Commented) (JIRA) -
David White (Created) (JIRA)
-
David White (Updated) (JIRA)
-
Remy Maucherat (Commented) (JIRA)
-
Remy Maucherat (Resolved) (JIRA)