Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 2037 invoked from network); 10 Dec 2001 01:16:04 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 10 Dec 2001 01:16:04 -0000 Received: (qmail 10450 invoked by uid 97); 10 Dec 2001 01:16:04 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 10418 invoked by uid 97); 10 Dec 2001 01:16:03 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 10405 invoked by uid 50); 10 Dec 2001 01:16:02 -0000 Date: 10 Dec 2001 01:16:02 -0000 Message-ID: <20011210011602.10404.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: tomcat-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 4828] - getSession(true) gets last valid session iven if invalidated during same request X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4828 getSession(true) gets last valid session iven if invalidated during same request craig.mcclanahan@sun.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME ------- Additional Comments From craig.mcclanahan@sun.com 2001-12-09 17:16 ------- This works for me against the 4.0.1 release code as well as against the current development branch. In addition, one of the unit test cases (Session04.java) does exactly this operation -- invalidate an old sesion, create a new one, and ensure that you got a different session. Could you try this against the 4.0.1 release code and reopen the bug (with a reproducible test case) if it still fails for you? -- To unsubscribe, e-mail: For additional commands, e-mail: