On 11/03/2014 14:16, Clemens Wyss DEV wrote: > Hi all, > we are still facing this issue here > https://issues.apache.org/bugzilla/show_bug.cgi > as Mark Thomas points out > https://issues.apache.org/bugzilla/show_bug.cgi?id=51872#c16 > the bug is "fixed". > > Trying to find out "what we are doing wrong" I have the following questions: > 1) as soon as a response is commited we should no longer access the > corresponding request?
There are no such restrictions. > 2) a response is commited (at latest) as soon as a byte is written into the > response's writer? A response is committed when the first byte is sent to the client. > 3) which "members" of the request are "volatile"? Are these specified in the > ServletRequest API? Define what you mean by volatile. The typical causes of this type of issue is retaining a reference to a request and/or response (in a filter, in a session or similar) and then trying to use the request or response object when processing a different request/response pair. It would help if you told us which Tomcat version you were using. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
