Re: TCP connections reuse

2015-06-16 Thread Mark Thomas
rs List > Date: Tuesday 16 June 2015 16:18 > To: Tomcat Users List > Subject: Re: TCP connections reuse > > On 16/06/2015 09:25, Maxim Neshcheret wrote: > Hi Christopher, > > > We actually found what was the problem with keep-alive. It is caused by the > fact

Re: TCP connections reuse

2015-06-16 Thread Maxim Neshcheret
Hi Mark We are using HTTP/1.1. BR, Maxim From: Mark Thomas Reply-To: Tomcat Users List Date: Tuesday 16 June 2015 16:18 To: Tomcat Users List Subject: Re: TCP connections reuse On 16/06/2015 09:25, Maxim Neshcheret wrote: Hi Christopher, We actually found what was the problem with

Re: TCP connections reuse

2015-06-16 Thread Mark Thomas
On 16/06/2015 09:25, Maxim Neshcheret wrote: > Hi Christopher, > > > We actually found what was the problem with keep-alive. It is caused by the > fact that Tomcat didn’t specify parameters ‘Keep-Alive: timeout=60,max=100’, > in HTTP header. In this case Java uses parameters by default, ie ‘K

Re: TCP connections reuse

2015-06-16 Thread Maxim Neshcheret
nnector but response header still does not contain these values. BR, Maxim From: Christopher Schultz Reply-To: Tomcat Users List Date: Saturday 13 June 2015 02:17 To: Tomcat Users List Subject: Re: TCP connections reuse -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Andy, On 6/12/15 12:35

Re: TCP connections reuse

2015-06-12 Thread Christopher Schultz
ang > [aw...@ptc.com] Sent: Friday, June 12, 2015 11:31 AM To: Tomcat > Users List Subject: Re: TCP connections reuse > > Could this be as simple as the default keepaliveTimeout = 15000 > (i.e. 15s) > > Andy > > On 06/12/2015 11:20 AM, Christopher Schultz wrote: M

RE: TCP connections reuse

2015-06-12 Thread Wang, Andy
Sorry, correction: default keepalivetimeout = connectionTimeout = 2 (20s) Andy From: Andy Wang [aw...@ptc.com] Sent: Friday, June 12, 2015 11:31 AM To: Tomcat Users List Subject: Re: TCP connections reuse Could this be as simple as the default

Re: TCP connections reuse

2015-06-12 Thread Andy Wang
Could this be as simple as the default keepaliveTimeout = 15000 (i.e. 15s) Andy On 06/12/2015 11:20 AM, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Maxim, On 6/12/15 1:53 AM, Maxim Neshcheret wrote: According to http://docs.oracle.com/javase/6/docs/technotes/gu

Re: TCP connections reuse

2015-06-12 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Maxim, On 6/12/15 1:53 AM, Maxim Neshcheret wrote: > According to > http://docs.oracle.com/javase/6/docs/technotes/guides/net/http-keepali ve.html > > connections in HTTP 1.1 >

Re: TCP connections reuse

2015-06-11 Thread Maxim Neshcheret
From: Christopher Schultz Reply-To: Tomcat Users List Date: Thursday 11 June 2015 09:12 To: Tomcat Users List Subject: Re: TCP connections reuse -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Maxim, On 6/10/15 4:12 AM, Maxim Neshcheret wrote: I have java http client which sends

Re: TCP connections reuse

2015-06-10 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Maxim, On 6/10/15 4:12 AM, Maxim Neshcheret wrote: > I have java http client which sends periodically (every 30 sec; > this code is run by heartbeat thread in the cycle) heartbeats > > *private* PostResponse post(String jSessionCookie, *final* Stri

TCP connections reuse

2015-06-10 Thread Maxim Neshcheret
I have java http client which sends periodically (every 30 sec; this code is run by heartbeat thread in the cycle) heartbeats private PostResponse post(String jSessionCookie, final String action, final String data, final int postTimeoutMs) throws IOException, SSYSException {