tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 36541] - session getAttribute/setAttribute and removeAttribute are NOT Thread safe.
Date Thu, 08 Sep 2005 06:50:58 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=36541>.
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-08 08:50 -------
(In reply to comment #20)
> As discussed on tomcat-dev after I reexamined StandardSession code further,
> adequate synchrnoization seems to be in place in the current Tomcat 5.5 code so
> that the infinite loop situation described in this issue does not occur. Please
> do not reopen the report.

Remy, sorry, but you are wrong. The read is the problem, not the write. During
the write process the hashmap is in flux, so if a read occurs at this time and
is not synchronized the thread which reads is killed.
So 5.5.x is as broken as 5.0.x is


-- 
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


Mime
View raw message