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

[noreply at bugs.horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: http://bugs.horde.org/ticket/13231
------------------------------------------------------------------------------
  Ticket           | 13231
  Aktualisiert Von | Jan Schneider <jan at horde.org>
  Zusammenfassung  | Hashtable session handler doesn't unlock on session close
  Warteschlange    | Horde Framework Packages
  Version          | Git master
  Typ              | Bug
  Status           | Feedback
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


Jan Schneider <jan at horde.org> (2014-05-28 14:32) hat geschrieben:

>> 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, that's how locking works. The question is, why is unlocking not  
working during the session.  
Horde_SessionHandler_Storage_Hashtable::close() should be called from  
PHP, and that should delete() the key from memcache again in  
Horde_Memcache::unlock().