2014-03-11 18:16 GMT+04:00 Clemens Wyss DEV <clemens...@mysign.ch>: > 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". >
Tomcat version = ? > 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 is no such requirement. A requirement is that you should not access it once request processing has been returned to Tomcat. Once request processing finishes, the request object is recycled by Tomcat and may be reused for a subsequent request. (The reuse can be disabled via a system property, see RECYCLE_FACADES. I usually do so, for better security). > 2) a response is commited (at latest) as soon as a byte is written into the > response's writer? No. It happens when you explicitly flush it, or a buffer overflows. It happens immediately of you have configured buffer size of 0. > 3) which "members" of the request are "volatile"? Are these specified in the > ServletRequest API? Not specified. (I am talking about "classic" Servlet API. No async processing.) --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
