<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>Horde_Session_Null causes session lock when using file based sessions.</title> 
  <pubDate>Fri, 10 Apr 2026 16:31:14 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/11809</link> 
  <atom:link rel="self" type="application/rss+xml" title="Horde_Session_Null causes session lock when using file based sessions." href="https://bugs.horde.org/ticket/11809/rss" /> 
  <description>Horde_Session_Null causes session lock when using file based sessions.</description> 
 
   
   
  <item> 
   <title>This isn&#039;t actually a bug, but I haven&#039;t seen it documented </title> 
   <description>This isn&#039;t actually a bug, but I haven&#039;t seen it documented anywhere. 
I&#039;m using Horde5 with Apache and mod_php. I&#039;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&#039;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.</description> 
   <pubDate>Mon, 03 Dec 2012 19:14:41 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/11809#t75377</link> 
  </item> 
   
  <item> 
   <title>Changes have been made in Git (master):

commit 645494515230</title> 
   <description>Changes have been made in Git (master):

commit 645494515230ddfd89b435c711e480e7b0468a0c
Author: Michael J Rubinsky &lt;mrubinsk@horde.org&gt;
Date:   Mon Dec 3 14:37:44 2012 -0500

    Immediately close the session when using Horde_Session_Null sessions.
    
    Avoids the potential for session lock issues. See Bug: 11809

 framework/Core/lib/Horde/Session/Null.php |    6 ++++--
 1 files changed, 4 insertions(+), 2 deletions(-)

http://git.horde.org/horde-git/-/commit/645494515230ddfd89b435c711e480e7b0468a0c</description> 
   <pubDate>Mon, 03 Dec 2012 19:38:58 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/11809#t75378</link> 
  </item> 
   
  <item> 
   <title>ActiveSync uses the Null session driver since it only needs </title> 
   <description>ActiveSync uses the Null session driver since it only needs a session long enough to ensure there is a session_id (some of the auth drivers need one for crypo functionality). I added code to immediately call session_write_close() after the session is created to avoid any locking issues.</description> 
   <pubDate>Mon, 03 Dec 2012 19:42:35 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/11809#t75379</link> 
  </item> 
   
  <item> 
   <title>Moving to Horde Base since it affects any code using Null se</title> 
   <description>Moving to Horde Base since it affects any code using Null sessions.</description> 
   <pubDate>Mon, 03 Dec 2012 19:44:01 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/11809#t75380</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
