DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16874>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16874 Same session for two different clients as a result of a lack in synchronization during recycling sessions ------- Additional Comments From [EMAIL PROTECTED] 2003-02-10 01:27 ------- That method doesn't look very well synced indeed. However, I don't see many cases where a race condition can occur on that particular method, and how the session can then get recycled twice. If you experienced the condition, I can add a sync in the expire method (which is the only place which calls recycle). Session recycling doesn't seem terribly useful overall (generation of the session id is likely to be at least as expensive as a few collection creation ...). --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
