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

* Your Email Address
* Spam protection	Enter the letters below: .__.. ..__ . ..__ \| \|\|_/ [__)\|__\|[__) \|__\|\| \\| \\| \|[__)
Comment	> 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
Attachment
Watch this ticket