| Summary | SQL session handler with hashtable cache enabled leads to fatal PHP errors |
| Queue | Horde Framework Packages |
| Queue Version | FRAMEWORK_5_1 |
| Type | Bug |
| State | Duplicate |
| Priority | 1. Low |
| Owners | |
| Requester | arjen+horde (at) de-korte (dot) org |
| Created | 03/27/2014 (4177 days ago) |
| Due | |
| Updated | 11/19/2014 (3940 days ago) |
| Assigned | 03/27/2014 (4177 days ago) |
| Resolved | 11/19/2014 (3940 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Duplicate
Database' and the checkbox next to 'Use a distributed hash table to
cache session information?' is selected. Which boils down to
$conf[sessionhandler][type] = 'Sql';
$conf[sessionhandler][hashtable] = true;
developed in the master branch.
State ⇒ Feedback
Also, if really using FRAMEWORK_5_1, please note that libraries are
developed in the master branch.
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ SQL session handler with hashtable cache enabled leads to fatal PHP errors
Queue ⇒ Horde Framework Packages
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
which means I had to get rid of APC for caching variables (since
that's no longer available). I installed memcache and configured it as
distributed hashtable. No problem.
I use SQL as session handler for quite a while already and since I now
had a distributed hashtable anyway, enabled it for caching session
information. Initially this seemed to work, but this combination fails
when opening Kronolith for instance:
[Wed Mar 26 19:31:57.147276 2014] [php5:error] [pid 6552] [client
192.168.1.121:39729] PHP Fatal error: Call to a member function
commit() on a non-object in
/usr/share/php5/PEAR/Horde/Db/Adapter/Pdo/Base.php on line 264,
referer: http://miffy.de-korte.org/horde/kronolith/
Using either SQL or distributed hashtable works, it is the combination
that fails.