Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 85287 invoked from network); 27 Jun 2002 14:38:50 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by 209.66.108.5 with SMTP; 27 Jun 2002 14:38:50 -0000 Received: (qmail 17147 invoked by uid 97); 27 Jun 2002 14:38:51 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 17126 invoked by uid 97); 27 Jun 2002 14:38:50 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 17113 invoked by uid 98); 27 Jun 2002 14:38:50 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) From: Bob Herrmann Message-Id: <200206271439.g5REdgl13575@jadn.com> Subject: Re: SessionTimeout Problem To: tomcat-dev@jakarta.apache.org Date: Thu, 27 Jun 2002 10:39:42 -0400 (EDT) In-Reply-To: <1025122371.23625.44.camel@hue.jadn.com> from "Bob Herrmann" at Jun 26, 2002 04:12:50 PM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: 209.66.108.5 1.6.2 0/1000/N X-Spam-Rating: 209.66.108.5 1.6.2 0/1000/N This is an update to my earlier email. Problem: setting session timeouts in 4.1.x's server.xml is pointless. Why: setting the Manager's attribute "maxInactiveInterval" or Contexts's attribute "sessionTimeout" is pointless because they get overwritten by the session timeout in the web.xml or if a web.xml is not present or the timeout is not defined, the 30 minute default value is taken from the config/web.xml defaults file. Solution: Not sure... perhaps one of these... 1. Remove the attributes from Manager and Context. And update the doc. 2. Remove the default value of 30 from the config/web.xml and update the doc for Manager to mention it can be overridden by the web.xml Ideas? Cheers, -bob > Problem: setting the "maxInactiveInterval" on the Manager tag > doesn't work. > > Why, well the problem is that two objects think they own the same > information. Namely, the Context and the session Manager both claim to > own the SessionTimeout. > > Each object has these properties. > > Manager.maxInactiveInterval is the session timeout in "seconds" > > Context.sessionTimeout is timeout in "minutes" > > > The digester creates a Manager (and may correctly set it's > maxInactiveInterval) and then binds it to a Container (Context.) The > Context overwrites the Manager's maxInactiveInterval with it's own > sessionTimeout. > > Once bound to a container, the Manager watches the sessionTimeout > property changes and adjusts its own maxInactiveInterval value to > track it (Useful when the web.xml is processed and the digester updates > the Context's sessionTimeout) > > Not sure how to correctly proceed. The Manager isn't bound to > a container when it's maxInactiveInterval is set by the digester, > so it cant tell the Context to use its value. > > Any ideas? > > Cheers > -bob > > > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > Cheers, -bob -- To unsubscribe, e-mail: For additional commands, e-mail: