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 03:25:02 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 craig.mcclanahan@sun.com  2005-09-08 05:25 -------
(In reply to comment #15)
> Why not keep everybody happy, simply make the session management class a
> configurable option at both Server and Context level, if the TC developers wish
> to "experiment" they can configure the un-synchronized access they so desire.
> 

Actually, the session management code *is* already configurable, albeit not
trivially.  You can include a <Manager> element inside your <Context> element
and create a custom implementation of the Manager interface that returns session
instances (probably subclassed from StandardSession) that do the locking for you.

The key question remains what the default behavior should be, and/or whether
there should be an easy boolean setting to turn this particular capability on or
off.


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