You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by James Nord <te...@teilo.net> on 2015/03/20 17:12:50 UTC
Issue with "Transfer-Encoding: chunked"
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-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Issue with "Transfer-Encoding: chunked"
Posted by James Nord <te...@teilo.net>.
On 13/06/2015 15:13, James Nord wrote:
> On 20/03/2015 16:12, James Nord wrote:
>>> 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...
>>
>> Is it possible for you to re-test with Tomcat 7.0.59? I don't see
>> anything in the changelog that seems to apply directly, but this might
>> be something that was fixed between 7.0.52 and 7.0.59.
>>
>> What connector are you using? Can you supply the (sanitized!)
>> <Connector> configuration from the server.sml?
>>
>> - -chris
>>
> I just realized I never circled back on this. Our customer upgraded
> to 7.0.59 and the issue has not happened since.
Dam sent to early. The connector was/is the standard out of the box
tomcat configuration.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Issue with "Transfer-Encoding: chunked"
Posted by James Nord <te...@teilo.net>.
On 20/03/2015 16:12, James Nord wrote:
>> 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...
>
> Is it possible for you to re-test with Tomcat 7.0.59? I don't see
> anything in the changelog that seems to apply directly, but this might
> be something that was fixed between 7.0.52 and 7.0.59.
>
> What connector are you using? Can you supply the (sanitized!)
> <Connector> configuration from the server.sml?
>
> - -chris
>
I just realized I never circled back on this. Our customer upgraded to
7.0.59 and the issue has not happened since.
Regards
/James
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Issue with "Transfer-Encoding: chunked"
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
James,
On 3/20/15 12:12 PM, James Nord wrote:
> 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...
Is it possible for you to re-test with Tomcat 7.0.59? I don't see
anything in the changelog that seems to apply directly, but this might
be something that was fixed between 7.0.52 and 7.0.59.
What connector are you using? Can you supply the (sanitized!)
<Connector> configuration from the server.sml?
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org
iQIcBAEBCAAGBQJVDGmsAAoJEBzwKT+lPKRYcs0QAKTEg5uHymVqyHhc16FW8s6m
ma3GVnGSJT3uj8XDEWqGkHgsGyA5nJeOOk5V1Kil0uyxSJIR1YcYjlUSOFPHM6w5
ldWZPNrRD7eW7Gmn4UyLBB8mXrBiNyLcUHrismpg0Mp7fPpOUvO/4GZqHei/e/kp
b1kIEB4V4Ndh5xMp0ipb+Yt2n5W3b9sm2UwxBB5z478QiGX7UJ08jAaQeWGIjOL0
BcFhUCBoPCYgG16BSLSrP5oIm8766q/g8YbBSjgCbFU15uH6lLbNBvGVC1v6T57A
LLNsZfy/djv3jYX+acFat56JfJdNI45mXrxKPeZtG8Jvn3C/BAfQMTqjlWIEfNsn
Su9pmlE0ZarIsbM/Ymo4+HD0MIMDw+UyGq5JRMDA8O58cEoRUvSGa4ZSIdCQZd3y
BPI4tqEFZX9qwOglj3nzcvHzafAhT+U22Sajw0D4mmRGF5gdorawHMfM9VCBXQyx
nuJ4PnHDVS/fskQJORrxF0xf7DpOfHVr6BJvOLIMDHIWPqNL4br16ingXKPeYiW4
e0VaJgnQi4J2eUD2uk/U9rNZ7+ajqQgak3gjTBK1Tk2cTnloMjwayTvm/1vE4z1X
JT+wUgvNVCLHjUypRCg6lWudkCY3/zSO+ctpDwQUqBNvmMoeqzjkHiOxMjg5ni7A
L3SDn3t51DDaTiizm+Sd
=JEhZ
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org