Tickets :: Comment on [#11809] Horde_Session_Null causes session lock when using file based sessions.

* Your Email Address
* Spam protection	Enter the letters below: .__ .__..__ .___.. . [__)[__][__) _/ \|__\| \| \\| \|\| \./__.\| \|
Comment	> This isn't actually a bug, but I haven't seen it documented anywhere. > I'm using Horde5 with Apache and mod_php. I've always chosen PHP file > sessions to make tests, for simplicity. > > When you choose push synchronization, your webserver uses a process > to look for changes requested, and that process lives until a change > is detected or until it reaches heartbeat seconds selected by ping > command. Unfortunately, with file sessions this means the session > file will be locked until process dies, so no other request from the > same device can be replied. It will wait until first process dies and > releases the lock on session file. > > I've seen this when trying to access gal while another process is > attending a previous ping command from the same device. As soon as > ping finishes, gal results appear on my device. > > If I choose memcache for sessions, these locking problems disappear, > and requests from same device are processed as soon as they arrive to > webserver. > This has been a very time consuming problem for me, as it prevents > activesync from normal operation, and I think it should be clearly > explained somewhere.
Attachment
Watch this ticket