It may be configurable, to allow both choices? André
-----Original Message----- From: GOMEZ Henri [mailto:[EMAIL PROTECTED]] Sent: 19 June 2002 10:26 To: Tomcat Developers List Subject: RE: [PATCH] When Session Max reached, throw out oldest session >Agreed... If we start invalidating sessions when too much memory is >"wasted", I'm going to choose a different servlet engine for >my 10m req/day >site... :) If I define that a session has a timeout, I want >that timeout to >be _real_ and if I run into memory problems, well, that's my >problem, not >yours (servlet engine developers)... > I agree. If there is no more slots open for incoming connections (clients), then the servlet engine should return an error, which could be handled by a redirector like mod_jk or mod_webapp to forward the request to another Tomcat. I'm really against dropping existing sessions..... -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> **** DISCLAIMER **** "This e-mail and any attachments thereto may contain information which is confidential and/or protected by intellectual property rights and are intended for the sole use of the recipient(s) named above. Any use of the information contained herein (including, but not limited to, total or partial reproduction, communication or distribution in any form) by persons other than the designated recipient(s) is prohibited. If you have received this e-mail in error, please notify the sender either by telephone or by e-mail and delete the material from any computer. Thank you for your cooperation." -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
