Tickets :: Comment on [#13231] Hashtable session handler doesn't unlock on session close

* Your Email Address
* Spam protection	Enter the letters below: . . __.._. __.. . \|\ \|(__ \| (__ \|__\| \| \\|.__)_\|_.__)\| \|
Comment	>> You rather mean inside Horde_Memcache#lock()? > > Yes. When six processes attempt to lock the session data more or less > at the same time, at most one will succeed in doing so, while the > others sleep for 100 ms. If after that the session data is still > locked (or locked again), this repeats until all have completed. > >> Well if the Memcache object doesn't add() this lock key, that's >> probably nothing that Horde can handle. > > The lock is added.
Attachment
Watch this ticket