[horde] 'message not found' bug patch?

[Kevin Konowalec]

Eep!  We're running 4 round-robining servers to front-end horde with  
one back-end database server.  With SQL sessions if you get  
disconnected on one server you can continue on another without  
knowing the difference... not so much with PHP based sessions... Is  
there a recommended configurations for multiple front-ends?


On Aug 22, 2005, at 9:48 AM, Michael M Slusarz wrote:


> Quoting Kevin Konowalec <kevin at ualberta.net>:
>
>
>
>>
>> Is there a patch for bug#1580?  My users are complaining furiously
>> about getting "message not found" the first time they click a
>> message.  I have upgraded to the latest version of Horde and am still
>> running imp 4.0.3... can we patch this or do I have to wait for the
>> next release of Imp?
>>
>>
>
> Neither.  You must use sessionhandler = 'none' (i.e. use PHP's
> file-based sessionhandler).  All the SQL-based sessionhandlers are
> still untested and initial reports indicate the code chuck put in to
> prevent concurrent session access doesn't work in 100% of the cases.
>
> michael
>
> _______________________________________
> Michael Slusarz [slusarz at curecanti.org]
> -- 
> Horde mailing list - Join the hunt: http://horde.org/bounties/#horde
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: horde-unsubscribe at lists.horde.org
>
>
>