First of all: thanks for the quick replies! I appreciate very much. > It would help if you told us which Tomcat version you were using. Tomcat 7.0.52, i.e. latest greatest
>(The reuse can be disabled via a system property, see RECYCLE_FACADES. I >usually do so, for better security) Would I need to compile my own tomcat? > Define what you mean by volatile. the members of the request object that are "recycled". To be honest, I have not yet looked into the tomcat sources. To render we use velocity. The output is directly rendered into the response-writer. So the first byte written/rendered by velocity sets the response to commited (right?). AND yes we have templates which we access the request#getRemoteAddress ("somewhere close the end"). So could it be that these "accesses" set the remoteAddress tot he caller oft he "previous request"? Thx Clemens -----Ursprüngliche Nachricht----- Von: Mark Thomas [mailto:ma...@apache.org] Gesendet: Dienstag, 11. März 2014 15:34 An: Tomcat Users List Betreff: Re: request.getRemoteAddr() sometimes returning IP address from the previous request 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 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org