tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re: Tomcat and "Chunked Transfer-Encoding"
Date Wed, 05 Feb 2014 10:11:22 GMT


Let's see what this gives.


From:   Konstantin Kolinko <>
To:     Tomcat Users List <>, 
Date:   03/02/2014 19:58
Subject:        Re: Tomcat and "Chunked Transfer-Encoding"

2014-02-03 Mark Thomas <>:
> On 03/02/2014 12:46, wrote:
>> I can't reproduce it with simple web application, it happens in one of 
>> applications, SDL WorldServer application which we bought for
>> translations. Even there the issue is random.

1. When response mixups happen, the first thing I would recommend is
to set the following system property (you can add it to file):



That will make your configuration more secure (at price of some
performance) and will raise the chances that meddling with
requests/response objects outside of their lifecycle would not go

Then look for any odd messages in the log files. E.g. attempts to write to 
closed stream, or an IllegalStateException, etc

A known culprit is javax.imageio.ImageIO API

So far it looks like an application issue, as Mark mentioned.

2. The convention on this mailing list is to do not top-post.
-> 6.

3. What connector implementation are you using?


I guess that you use HTTP and are behind an HTTP proxy.

4. Do you use any Asynchronous IO, Comet, WebSockets (e.g. via
Atmosphere framework)?

5. In your traffic snippet,
does that HTML response match the request, or a previous request?

What generates those "scrollTo"  script fragments?

6. Note that you can configure AccessLogValve to log your thread name 

Best regards,
Konstantin Kolinko

To unsubscribe, e-mail:
For additional commands, e-mail:

This e-mail may contain confidential information.
If you are not an addressee or otherwise authorised to receive this message, you should not
use, copy, disclose or take any action based on this e-mail. 
If you have received this e-mail in error, please inform the sender promptly and delete this
message and any attachments immediately.
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message