Ahhh, that explains it. I've been meaning to look into why my first request
takes so damned long.
I just added the following line of code to the init() method of one of load
on startup servlets and now my first requests goes through just fine.
new java.security.SecureRandom().nextLong();
Now, I realize this is something of a hack. Would it make sense to add
something to the session id generation code to initialize the rander number
generator when a Web Apps loads. If other developers think this is a
reasonable idea I'll post a patch.
-----Original Message-----
<snip>
One change that affects the first request to an app (more precisely, the
first
request that creates a session) is the way session ids are calculated.
Tomcat
3.2 now uses the java.security.SecureRandom class for this, which (on some
platforms) can take many seconds to initialize itself the very first time it
is
called.
Craig McClanahan
