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 Fri, 09 Sep 2005 11:28:51 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 darryl@darrylmiles.org  2005-09-09 13:28 -------
(In reply to comment #66)
> http://java.sun.com/j2se/javadoc/writingapispecs/index.html#top-level

That reference is invalid in the context of this bug report.  I read it to be a
hyperthetical example of what to put inside javadoc information.

Nothing concrete to under pin all Java programming design.


My comments fallback to what is written (and not written) into the documentation
for the HashMap implementation that TC has elected to use for the job.  It does
not say you call get() while you are also doing a put() (when the put() may
cause internal re-arangement), it explicitly warns you of this problem and as we
have no way knowing if the put will cause a rearrangment to achieve TCs goal of
robustness we have to synchronize our usage.


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