[Tickets #13904] Horde_Core 1.19.12 SQL SessionHandler does not work ( Reopen #13463)

[noreply at bugs.horde.org]

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

Ticket URL: https://bugs.horde.org/ticket/13904
------------------------------------------------------------------------------
  Ticket             | 13904
  Created By         | jcblanco at fi.upm.es
  Summary            | Horde_Core 1.19.12 SQL SessionHandler does not work (
                     | Reopen #13463)
  Queue              | Horde Groupware Webmail Edition
  Version            | 5.2.5
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


jcblanco at fi.upm.es (2015-03-09 12:37) wrote:

Hello again, I've just installed de last version (5.2.5) of Horde  
webmail and the problem with bug #13463 is still there and getting  
worse.
I think that I have some new information, the error is produced  
because a SessionHandler (Storage Sql) commit is started after the Db  
object has been disconnected.
The situation is produced when destructors (__destruct) are called for  
the  Db/Adapter/Base object (which is processed first and disconnects  
the database object) and for the SessionHandler object which calls to  
session_write_close and closes the session after the commit of the  
last active transaction, but in this moment the underlying Db object  
does no exists.

Seems that SessionHandler maintains an open active transaction all the  
time after the first read  I don't know if this can be modified or if  
there is a way to force an explicit close of SessionHandler before the  
object rundown