Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
From: bugzilla@apache.org
To: dev@tomcat.apache.org
Subject: DO NOT REPLY [Bug 52697] Response.recycle() does not always call
 outputStream.clear()
Date: Sat, 18 Feb 2012 01:19:28 +0000
Message-ID: <bug-52697-78-xDGnnAcgv0@https.issues.apache.org/bugzilla/>
In-Reply-To: <bug-52697-78@https.issues.apache.org/bugzilla/>
References: <bug-52697-78@https.issues.apache.org/bugzilla/>
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0

https://issues.apache.org/bugzilla/show_bug.cgi?id=52697

--- Comment #3 from Konstantin Kolinko <knst.kolinko@gmail.com> 2012-02-18 01:19:28 UTC ---
(In reply to comment #0)
> We recently had problem with requests/responses sometimes being mixed up in our
> Apache+Tomcat setup. It turned out that our 3rd party PDF generator software
> PD4ML, that we gave access to the HttpServletResponse.getOutputStream(), closed
> the stream from a finalize() method. This means that the JVM FinalizerThread
> unexpectedly called close() at some random later point in time.

A buggy third party library...

Note that Java ImageIO is known offender that has the same problem. It is on
the FAQ pages in the wiki - see there [1]. You may add your library to that
page.

[1] http://wiki.apache.org/tomcat/FAQ/KnownIssues

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org