6.0.0-git
2019-03-18

[#5684] session oversized for memcache
Summary session oversized for memcache
Queue Horde Framework Packages
Queue Version HEAD
Type Bug
State Resolved
Priority 2. Medium
Owners slusarz (at) horde (dot) org
Requester adrieder (at) sbox (dot) tugraz (dot) at
Created 2007-08-30 (4218 days ago)
Due 08/31/2007 (4217 days ago)
Updated 2007-09-05 (4212 days ago)
Assigned 2007-08-30 (4218 days ago)
Resolved 2007-09-05 (4212 days ago)
Milestone
Patch No

History
2007-09-05 15:30:46 Michael Slusarz Comment #3
Version ⇒ HEAD
Queue ⇒ Horde Framework Packages
State ⇒ Resolved
Reply to this comment
Committed, thanks.
2007-08-30 18:26:50 Chuck Hagenbuch Assigned to Michael Slusarz
State ⇒ Assigned
 
2007-08-30 17:54:22 adrieder (at) sbox (dot) tugraz (dot) at Comment #2
New Attachment: Memcache.php.patch Download
Reply to this comment
Found it! The attached patch to the memcache driver solves the problem!

We always wrote "number of slabs + 1", as the number of used slabs for 
oversized items to "horde_memcache_os".

This was no problem for caching items, but it was for sessions because 
the "get" method would then return "false" for the last item (slabs + 
1) which of coures does not exist. The session handler gets false and 
kicks out the logged in user.
2007-08-30 15:52:35 adrieder (at) sbox (dot) tugraz (dot) at Comment #1
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Summary ⇒ session oversized for memcache
Due ⇒ 2007-08-31
Queue ⇒ IMP
Reply to this comment
Maybe this is not the right place for the ticked but the problem is 
related to IMP.



We have a user with over 36,000 messages in his INBOX. If the 
sessionhandler is set to memcache, then the user will be logged out 
when trying to compose and send a new message after he/she logged in. 
It seems that the session gets destroyed somehow because of its size.



When I switch to the mysql sessionhandler the problem is gone. And I 
see that the session has a szie of ~2.8Mb. I thought that this shold 
not be a problem for the memcache cache driver anymore, at least not 
when using it for caching things. Is the storing of sessions handled 
differently?

Saved Queries