[imp] Re: Lots of Timeouts w/Horde & Imp

[Stanley Yuen]

The following are our experience.  Hopefully it can help to answer your
questions.

We had entered this problem and found that, even we increased number in the
session values below, we still received user report on session timeout
unexepctedly.   Thus we believed the timeout problem was not related these
values.

Finally, we throught we found the real cause.   It's because we put IMP in 2
or more servers and used DNS round-robin (i.e.  webmail.mydomain.edu mapped
to maila and mailb in DNS server) whereas session data were stored in a temp
directory in each machine separately.   If a user's PC directly connected to
the webmail machine using the hostname webmail.mydomain.edu, there should be
no session problem and the operating system would try to "cache" the real
hostname resolved in a single session.

However, if there were a lot of users trying to login webmail.mydomain.edu
behind a proxy server, session timeout problem became worse.   Probably the
PC's operating system could not "cache" the proper hostanme in a session as
the real hostname would change at the proxy server.  As the hostname was
changed, the user's session will be redirected to another server (but
actually the user did not login this server) and session timeout occurred.

In order to solve it, you may consider specifying a single place (a shared
directory via NFS or a database table) to keep your session data.
Moreover, if your PHP version is below 4.3, please try to upgrade it as some
session problems were idenitifed before.

Just my 2 cents.

Best wishes,
Stanley Yuen

-----Original Message-----
From: Myke Place [mailto:mp at xmission.com] 
Sent: Friday, January 09, 2004 3:46 AM
To: imp at lists.horde.org
Subject: Re: [imp] Re: Lots of Timeouts w/Horde & Imp


Are there recommended values for session.gc_maxlifetime and
session.cache_expire? I'm set to session.gc_maxlifetime = 28800 and 
session.cache_expire = 180 and I'm still seeing the occasional timeout. 
I have page compression turned off of course. 

-mp


* Jacob Davida (jacob-news at davida.com) [031202 12:13] spake thusly:
> I'm using
> 
> php.ini [Session] Settings:
> 
> session.save_handler = file
> session.gc_maxlifetime = 7200
> session.gc_probability = 1
> session.gc_divisor     = 100
> session.save_path = /tmp
> session.use_cookies = 1
> session.auto_start = 0
> session.cookie_lifetime = 0
> session.cookie_path = /
> session.entropy_length = 0
> session.cache_limiter = nocache
> session.cache_expire = 600
> session.use_trans_sid = 0
> 
> Thanks for the suggestion., though I dont think the sessions are being 
> garbage collected... I think the user would see the page telling them 
> their session has expired in that case. I've been digging quite a bit  
> :)
> 
> - Jacob
> 
> "Daniel Eckl" <daniel.eckl at gmx.de> wrote in message 
> news:20031202190242.0wtj48ck04w4oww0 at localhost...
> > Perhaps session.gc_maxlifetime in php.ini is set too short. In this 
> > case
> the
> > sess_* files will be deleted as garbage before the session should be 
> > ended
> as
> > thought.
> >
> > Greets,
> > Daniel
> >
> >
> 
> 
> 
> 
> --
> IMP mailing list
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: imp-unsubscribe at lists.horde.org
> 

-- 
IMP mailing list
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: imp-unsubscribe at lists.horde.org