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

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/13231
------------------------------------------------------------------------------
  Ticket             | 13231
  Updated By         | arjen+horde at de-korte.org
  Summary            | Hashtable session handler doesn't unlock on session
                     | close
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


arjen+horde at de-korte.org (2014-05-28 11:13) wrote:

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