Hi all,
We have a webapp that when run with tomcat (7.0.52) on a certain host
after a period of time has issues with chunking.
The issue is that the terminating Zero length chunk is not sent by
tomcat even though looking at the last chunk the data is complete.
Whilst at first glance this would appear to be our webapp not finishing
the request correctly tomcat initiates a TCP level close on the
connection 20s after the last chunk has been sent. This 20s corresponds
to the keepalive timout so it appears as though Tomcat thinks it is
waiting for the next request to come from the client (and the client is
still waiting for the terminating chunk).
I have written a simple webapp with a servlet that behaves badily in
various different ways I can image - and if the serverlet does not
return from the doGet method then tomcat will not try and close the tcp
connection and it remains open for a long time.
We have ruled out network appliances/proxies/ssl and are seeing this
when we talk directly to the tomcat http port.
The more I look into this the more I think it appears to be a tomcat
issue (we have had 3 reports of this and only when our app is run in
Tomcat).
I'm stuck now as to where I could possible look to get more information
or if there is any extra logging in tomcat that I could enable around
this area (I looked but didn't see any) to try and narrow the cause down
to an area of Tomcat or our app. So I am reaching out with the hope
that someone has some ideas...
Thanks in advance
/James
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org