Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 22043 invoked from network); 13 Jun 2002 11:47:59 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 13 Jun 2002 11:47:59 -0000 Received: (qmail 7975 invoked by uid 97); 13 Jun 2002 11:47:54 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 7959 invoked by uid 97); 13 Jun 2002 11:47:54 -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 7947 invoked by uid 98); 13 Jun 2002 11:47:53 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Subject: Re: [PROPOSAL] When Session Max reached, throw out oldest session From: Bob Herrmann To: Tomcat Developers List In-Reply-To: <4.3.2.7.2.20020613102634.03b8ac70@pop3.demon.co.uk> References: <4.3.2.7.2.20020613102634.03b8ac70@pop3.demon.co.uk> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 13 Jun 2002 07:51:47 -0400 Message-Id: <1023969107.2559.16.camel@hue.jadn.com> Mime-Version: 1.0 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Thu, 2002-06-13 at 03:43, Kief Morris wrote: > bob@jadn.com typed the following on 05:22 PM 6/12/2002 -0400 > >PROPOSAL: When Session Max reached, throw out oldest session > ... > >1. When the maximum number of sessions is reached, change > >StandardManager from throwing an IllegalStateException exception, to > >expiring the Least Recently Used (LRUMap) session. > > I'm not 100% comfortable with this, if a server sets the max sessions > too low and gets a lot of activity, the behavior will be confusing - users > will unexpectedly lose logins or whatever their session data is, and it > might be taken for a bug by the administrator. I guess I'll be happy as > long as we log a warning when sessions are thrown out due to max > sessions being exceeded. Good idea, I will be sure to log the expiration event, and I will also ensure that the admin documentation is updated to explain this behavior. Cheers, -bob -- To unsubscribe, e-mail: For additional commands, e-mail: