You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2010/06/12 13:28:30 UTC
DO NOT REPLY [Bug 49431] New: keep-alive is not working for tomcat
with HTTP/1.1 when Connection header is not present
https://issues.apache.org/bugzilla/show_bug.cgi?id=49431
Summary: keep-alive is not working for tomcat with HTTP/1.1
when Connection header is not present
Product: Tomcat 6
Version: 6.0.20
Platform: PC
OS/Version: Solaris
Status: NEW
Severity: major
Priority: P2
Component: Manager application
AssignedTo: dev@tomcat.apache.org
ReportedBy: vinodsridhar1981@gmail.com
Created an attachment (id=25590)
--> (https://issues.apache.org/bugzilla/attachment.cgi?id=25590)
The snoop behaviour when apache xmlrpc http client is used
I have configured the server.xml to have the following configuration
<Connector port="11030" protocol="HTTP/1.1"
connectionTimeout="60000" maxThreads="150"
maxKeepAliveRequests="-1"
redirectPort="11033" />
Using apache xmlrpc client scenario
-------------------------------------
I am having a apache xmlrpc servlet running on Tomcat which responds for the
apache xmlrpc client .I could see the following HTTP Post is happening
POST /VoucherUsage HTTP/1.1
Content-Type: text/xml
User-Agent: Apache XML RPC 3.0 (Jakarta Commons httpclient Transport)
Authorization: Basic dnM6dnM=
Host: 147.128.136.46:11030
Content-Length: 503
when i see the messages in packet sniffer.I see the tomcat is intitating a TCP
FIN to terminate connections from the client.
Using jmeter client scenario
-----------------------------
I also tested the same scenario using jmeter client .When keep-alive is set it
is working fine.Here the tomcat is not intiating the TCP FIN.The difference i
found is that it sends a Connection header with keep-alive message.
POST /VoucherUsage HTTP/1.1
Connection: keep-alive
User-Agent: AIR Server/2.0/1.0
authorization: Basic ZXJpY3Nzb246ZXJpY3Nzb24xMjM=
Host: 147.128.136.46:11030
Content-Length: 997
Content-Type: text/xml; charset=utf-8
Tomcat in HTTP/1.1 is not providing keep-alive by default without the
Connection header.Please fix this
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
DO NOT REPLY [Bug 49431] keep-alive is not working for tomcat with
HTTP/1.1 when Connection header is not present
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=49431
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #1 from Mark Thomas <ma...@apache.org> 2010-06-13 16:20:53 EDT ---
The attached trace clearly shows the commons httpclient has not been configured
for keep-alive since it creates a new connection for each request.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
DO NOT REPLY [Bug 49431] keep-alive is not working for tomcat with
HTTP/1.1 when Connection header is not present
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=49431
vinod <vi...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vinodsridhar1981@gmail.com
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org