https://issues.apache.org/bugzilla/show_bug.cgi?id=48855
Konstantin Kolinko <knst.koli...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
Severity|critical |normal
--- Comment #1 from Konstantin Kolinko <knst.koli...@gmail.com> 2010-03-04
11:58:31 UTC ---
Bugzilla is not a support forum. Please use the Tomcat users mailing list.
> We have synchronized the request.setHeader(…)
A lot depends on how you did that and what the actual code is. In general, you
must not access "response" object from several threads, or keep references to
it beyond the request processing cycle, regardless of what methods of the
request/response you are calling. E.g. your stacktraces are triggered by
response.getWriter().write() and by response.reset() respectively. (reset()
here is called to discard preceding output before showing an error page).
Thus far, there were several similar reports on users@, but the error was
always in the application code, not in Tomcat. See e.g.
http://marc.info/?t=126658414500001&r=1&w=2
and other similar threads.
If you can provide some valid sample application that reproduces the issue,
feel free to reopen it.
--
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-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
