Looking at tcpdumps it looks like the client side is timing itself out best I can tell, I clicked on compose, and then 5 minutes later it errored out:
Any idea how I might verify what the problem is? I'm not seeing anything popping up in the error logs and I'm not able to reproduce this myself, I'm going off reports from customers2012/2/14 Jernej Porenta <jernej.porenta@arnes.si>I don't think that is the actual issue if your cluster members have time in sync, since session functions use this SQLs (program/include/rcube_session.php):
On Feb 14, 2012, at 6:21 PM, James Devine wrote:
> My fear is that the garbage collection from one or more webmail machines is somehow stomping over active sessions
- db_destroy (kill session; logout etc): DELETE FROM %s WHERE sess_id = ?
- db_gc (garbage collector): DELETE FROM %s WHERE changed < %s
Our problem is that cached information (cache_messages, etc) does not get purged automatically, but I don't know what is the deal about that.
LP, Jernej