Tickets :: [#12254] Session data written on every access

6.0.0-alpha14

7/2/25

Summary	Session data written on every access
Queue	Horde Framework Packages
Queue Version	Git master
Type	Bug
State	Resolved
Priority	2. Medium
Owners	Horde Developers (at) , slusarz (at) horde (dot) org
Requester	slusarz (at) horde (dot) org
Created	05/14/2013 (4432 days ago)
Due
Updated	05/29/2013 (4417 days ago)
Assigned
Resolved	05/29/2013 (4417 days ago)
Github Issue Link
Github Pull Request
Milestone	5.1
Patch	No

05/29/2013 05:46:28 AM	Michael Slusarz	Comment #7 State ⇒ Resolved	Reply to this comment
There's still concerns about apps (e.g. IMP) that change session data all the time. I.e. any mailbox action can cause a session change, since mailbox data is stored in the session. However... this data has previously been optimized for size and the alternative - stratight cache - is not a distinctly better option at this time. Since doing things like navigating through Horde and polling the mailbox no longer cause session writing, I'm closing this ticket since it was referring to the critical issue of the session data being overwritten 100% of the time for no reason.

05/14/2013 11:13:44 PM	Michael Slusarz	Comment #6 Assigned to Michael Slusarz Summary ⇒ Session data written on every access Priority ⇒ 2. Medium	Reply to this comment
The worst offenders (language, notification) have been dealt with. Now am not seeing a session write on every page load. Still need to investigate a bit more to find any other problem setters.

05/14/2013 11:12:12 PM	Git Commit	Comment #5	Reply to this comment
Changes have been made in Git (master): commit 69bf6dfdd0ed34e5cb0fea5dc3034dddcb4b9e8a Author: Michael M Slusarz <slusarz@horde.org> Date: Tue May 14 17:10:45 2013 -0600 ~~Bug #12254~~: Don't store empty notification array to session .../Horde/Core/Notification/Storage/Session.php \| 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) http://git.horde.org/horde-git/-/commit/69bf6dfdd0ed34e5cb0fea5dc3034dddcb4b9e8a

05/14/2013 11:01:46 PM	Git Commit	Comment #4	Reply to this comment
Changes have been made in Git (master): commit 06562fe48c40bc10247677cdd4bc88f0670a5f2a Author: Michael M Slusarz <slusarz@horde.org> Date: Tue May 14 17:00:02 2013 -0600 ~~Bug #12254~~: Don't blow away nls config on every page load if the language didn't change framework/Core/lib/Horde/Registry.php \| 15 +++++++++++---- 1 files changed, 11 insertions(+), 4 deletions(-) http://git.horde.org/horde-git/-/commit/06562fe48c40bc10247677cdd4bc88f0670a5f2a

05/14/2013 11:01:42 PM	Git Commit	Comment #3	Reply to this comment
Changes have been made in Git (master): commit d50573529390ce685fd4382f481cd6650da383e3 Author: Michael M Slusarz <slusarz@horde.org> Date: Tue May 14 16:51:08 2013 -0600 ~~Bug #12254~~: Smarter session storage; only trigger change if given value is different framework/Core/lib/Horde/Session.php \| 22 ++++++++++++---------- 1 files changed, 12 insertions(+), 10 deletions(-) http://git.horde.org/horde-git/-/commit/d50573529390ce685fd4382f481cd6650da383e3

05/14/2013 10:40:44 PM	Michael Slusarz	Comment #2	Reply to this comment
May have jumped the gun a bit regarding the "lost" data. Looks like the data is being deleted instead. On every access (this is just a refresh of a mailbox in IMP), I am seeing the following: ADD horde language REMOVE horde nls/curr_charset REMOVE horde nls/ ADD horde nls/valid_en_US ADD horde language REMOVE horde nls/curr_charset REMOVE horde nls/valid_en_US REMOVE horde nls/ ADD horde language REMOVE horde nls/curr_charset REMOVE horde nls/ ADD horde notify/status ADD horde nls/valid_en_US ADD horde language REMOVE horde nls/curr_charset REMOVE horde nls/valid_en_US REMOVE horde nls/ REMOVE horde notify/status REMOVE horde notify/_unattached ADD imp logintasks

05/14/2013 05:23:20 PM	Michael Slusarz	Comment #1 Priority ⇒ 3. High Type ⇒ Bug Summary ⇒ CRITICAL: Session data written on every access/session data lost Queue ⇒ Horde Framework Packages Assigned to Horde Developers Milestone ⇒ 5.1 Patch ⇒ No State ⇒ Assigned	Reply to this comment
The session is being written on every page load. Even worse - the reason it appears to be doing this is because session data is being lost. Can verify with multiple backends, so it is not a sessionhandler backend issue. Not sure how long this has been occurring, since I only recently added logging to all sessionhandler backends.