tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <>
Subject Re: Responses of two different requests concatinated
Date Wed, 07 Aug 2013 22:10:55 GMT
Hash: SHA256


On 8/7/13 6:23 AM, Marvin Lillehaug wrote:
> We recently got an error report from a user of one of the systems
> we have developed, showing that the response from a different
> request had been appended to the original response. The original
> response was the front page of a site, generated with jsp, and the
> appended response was a excel file generated a few seconds
> earlier.

> Our current hypothesis is that some buffer in either httpd(2.2.22)
>  or Tomcat (7.0.35) has been recycled.

Note that the Tomcat documentation uses the word "recycled" with
respect to connections and façades to mean "not re-used". You appear
to be using the term "recycled" to mean "re-used". I just wanted to be
clear because there is a related system property that uses the term
"recycle" (see below).

> Httpd is connected to Tomcat using http proxypass.

First, you should probably upgrade Tomcat to the latest 7.0 version
which is 7.0.42. Is that a possibility?

Second, you should post your whole <Connector> configuration from
Tomcat (minus any sensitive information of course).

If you want a possible quick-fix, you should look at the
RECYCLE_FACADES system property documented here:

If you set that system property to "on", then potential
response-leakages should be significantly reduced at a slight cost in
terms of heap and GC activity (but fairly negligible, as request
façades shouldn't really be surviving any minor collections... they
will just cause minor collections to occur more often).

> I have started trying to reproduce the problem, but thought I
> should try the mailing lists of both httpd and tomcat before
> continuing.

While that's okay, we generally prefer not to cross-post. Here, I have
replied only to the Tomcat users' mailing list as my reply is

> What I have done thus far is: concatenating html and excel to
> verify that it is possible to open and looks the way the user
> experienced; building a custom version of Tomcat that uses the same
> Processor for each request and configured to use only one thread.
> This seems a bit similar to the issue described in 

This is not likely to be your problem, but we'll see when you post
your configuration.

> Some results when googleling suggests that this could happen when
> jsp tags are not coded properly, but I have not found any such code
> in our applications.

Any references? I'm not familiar with any suggestions that JSP tags
are leaky in any way. Are you using any JSPs in these transactions
that appear to have been mixed-up? I'd be surprised to find a JSP that
produces an XLS document.

- -chris
Version: GnuPG v1.4.14 (Darwin)
Comment: GPGTools -
Comment: Using GnuPG with Thunderbird -


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

View raw message