Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@www.apache.org Received: (qmail 30646 invoked from network); 9 Sep 2005 12:49:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 9 Sep 2005 12:49:43 -0000 Received: (qmail 45990 invoked by uid 500); 9 Sep 2005 12:49:34 -0000 Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 45967 invoked by uid 500); 9 Sep 2005 12:49:33 -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 45954 invoked by uid 99); 9 Sep 2005 12:49:33 -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; Fri, 09 Sep 2005 05:49:33 -0700 Received: by ajax.apache.org (Postfix, from userid 99) id 6CFA132E; Fri, 9 Sep 2005 14:49:32 +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: <20050909124932.6CFA132E@ajax.apache.org> Date: Fri, 9 Sep 2005 14:49:32 +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 struts_user@anotheria.net 2005-09-09 14:49 ------- (In reply to comment #65) > Leon, > > Can you publish your TC+HashMap finding you based your comment #55 ? It's a simple program, which actually shows the bug (on synchronized put/remove and unsychronized get). I am to stupid to program the writers to stop as soon as the loop occurs, so they fix the problem some time after it occurs (thats why a long loop instead of infinite loop). After each execution the reader measures how long the execution lasted. If the execution lasted longer then 5 seconds it cries. The mid time of the execution is 0.05 milliseconds. So we can safely assume, that executions which last 5 seconds or more aren't normal. In fact I had it all night running with 714 "too long executions", longest of them being 70 seconds. If I add synchronized(map) in the getAttribute method of the Storage class it doesn't occure anymore. -- 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