Return-Path: Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 30025 invoked from network); 12 Feb 2001 10:16:45 -0000 Received: from smtp.bvdep.com (HELO smtp.bvd) (193.194.158.46) by h31.sny.collab.net with SMTP; 12 Feb 2001 10:16:45 -0000 Received: from SMTP ([172.28.2.46]) by smtp.bvd with Microsoft SMTPSVC(5.5.1877.197.19); Mon, 12 Feb 2001 11:16:56 +0100 Received: from mail.bvdep.com ([172.28.2.8]) by 172.28.2.46 (Norton AntiVirus for Internet Email Gateways 1.0) ; Mon, 12 Feb 2001 10:16:56 0000 (GMT) Received: from bvdep.com (LVL-NTW40 [172.28.64.205]) by mail.bvdep.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id 1NLH7YHR; Mon, 12 Feb 2001 11:16:55 +0100 Message-ID: <3A87B80D.A2D02446@bvdep.com> Date: Mon, 12 Feb 2001 11:16:45 +0100 From: Luc Vanlerberghe X-Mailer: Mozilla 4.73 [en] (WinNT; U) X-Accept-Language: en,nl,nl-BE,es MIME-Version: 1.0 To: tomcat-user@jakarta.apache.org Subject: Re: req.getSession(true) problems with 3.2.1 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N I don't know about the first problem, but the fact that the initial getSession is slower than before is due to the fact that the sessionid is now generated useing a java.security.SecureRandom object. The initialisation of objects that class take a while to initialise to make sure their state is not predictable... This delay should only occur for the first session though. I believe the latest (development) versions of tomcat (both 3.x and 4.x) initialise this generator on startup instead of waiting for the first session. However, you can configure them to use the normal java.util.Random class instead during development. Search the archives for keywords like session, SecureRandom, server.xml etc... Luc Vanlerberghe Richard Downey wrote: > > Hi, > > I am moving working applications from 3.1.1 to 3.2.1 and after getting over > the strictly enforced case rules everything seemed to be OK , however I've > noticed that whenever a session expires using HttpSession session = > req.getSession(true); seems to trigger a loop leading to a stack overflow. > This can be replicated and the problem disappears when I switch back to > 3.1.1 . Has anybody else noted anything similar ? I'm running Sun JDK 2 1.3 > on Windows 2000. > > I have also observed that the initial getSession is slower than under 3.1.1 > (5 seconds 3.2.1 versus a time in milliseconds for 3.1.1) I've checked that > it wasn't some kind of cookie conflict between 3.1.1 and 3.2.1 by getting > rid of the cookies. Any ideas would be gratefully received. > > Regards > > Richard Downey > Contenlo > > --------------------------------------------------------------------- > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org > For additional commands, email: tomcat-user-help@jakarta.apache.org