Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@www.apache.org Received: (qmail 80322 invoked from network); 8 Sep 2005 03:32:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 8 Sep 2005 03:32:29 -0000 Received: (qmail 70712 invoked by uid 500); 8 Sep 2005 03:32:24 -0000 Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 70689 invoked by uid 500); 8 Sep 2005 03:32:24 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: 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 70667 invoked by uid 99); 8 Sep 2005 03:32:23 -0000 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Sep 2005 20:32:22 -0700 Received: by ajax.apache.org (Postfix, from userid 99) id 2C521130; Thu, 8 Sep 2005 05:32:20 +0200 (CEST) From: bugzilla@apache.org To: tomcat-dev@jakarta.apache.org Subject: DO NOT REPLY [Bug 36541] - session getAttribute/setAttribute and removeAttribute are NOT Thread safe. X-Bugzilla-Reason: AssignedTo Message-Id: <20050908033220.2C521130@ajax.apache.org> Date: Thu, 8 Sep 2005 05:32:20 +0200 (CEST) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.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://issues.apache.org/bugzilla/show_bug.cgi?id=36541 ------- Additional Comments From craig.mcclanahan@sun.com 2005-09-08 05:32 ------- (In reply to comment #8) > (In reply to comment #7) > > I would agree that neither implementation is buggy -- it is entirely legal for a > > servlet container to avoid letting an application corrupt its interna data > > structures. It's too bad that the current Tomcat developers care more about > > performance than they care about reliability. > > Of course. Thankfully, you guys have glassfish now for good reliability, so you > don't have to deal with these loony Tomcat developers anymore ;) > Apparently it is indeed a good thing :-). The appropriate patch was just committed to the Glassfish repository. If people want an open source implementation of the servlet spec where the developers listen to users on issues like this, you might want to browse over to: https://glassfish.dev.java.net and take a look. > > If you aren't going to change it back to the 4.1 implementation (with > > synchronization locks around the accesses), please take my name out of the > > @author tag for org.apache.catalina.session.StandardSession -- this code does > > *not* represent anything I wish to be associated with. > > Sure, I have no problem with that if it's your wish. > This (removing my name from the @author tag on StandardSession), both here and everywhere else in the Tomcat code base, would indeed be my wish. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org