Phil, are you sure that youre new value for *SESSION-MAX-TIME* is used by your sessions? Try tracing HUNCHENTOOT::SESSION-TOO-OLD-P and check the log file for entries saying "Session with ID <id> too old". If you see those messages in the log, or if HUNCHENTOOT::SESSION-TOO-OLD-P returns a true value for a session, your *SESSION-MAX-TIME* change has not been seen by Hunchentoot. One reason could be that you're changing the value of the global variable after you started Hunchentoot in multi-threaded mode. In that case, the changed value might not be picked up. Let us know how you proceed. -Hans On Wed, May 19, 2010 at 12:46, Phil Marneweck <zaries@global.co.za> wrote: > Hi > > Is there any thing more than *session-gc-frequency* and > *session-max-time* that influences session time outs? > > Because it does not matter how high I set these values the session keeps > on timing out with in a couple of minutes! > > Can those values be set at any time or do they have to be set before any > acceptors are created? > > Any help would be much appreciated this is causing me major pain on a > live site. > > > > > > > _______________________________________________ > tbnl-devel site list > tbnl-devel@common-lisp.net > http://common-lisp.net/mailman/listinfo/tbnl-devel > _______________________________________________ tbnl-devel site list tbnl-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-devel