tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Luc Vanlerberghe <>
Subject Re: req.getSession(true) problems with 3.2.1
Date Mon, 12 Feb 2001 10:16:45 GMT
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 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
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:
> For additional commands, email:

View raw message