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 [EMAIL PROTECTED] 2005-09-08 18:14 ------- (In reply to comment #50) > That was the purpose of the second get check inside the sync block. The > second > request will, if the cache is null, block on the sync'd session, and only > proceed into the sync block after the put. The first thing it does is check > again, which returns non null and it continues happily. The situation can occur IF the second request overtakes the first that Object cached = session.get(key) will simply not come back and return null, because it hangs in the hashmap inside the get and so your check for null will never be called -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
