> -----Original Message-----
> From: Caldarale, Charles R [mailto:Chuck.Caldarale@(protected)]
> Sent: Thursday, December 28, 2006 8:25 PM
> To: Tomcat Users List
> Subject: RE: session#getId changes during doGet invocation under heavy
> load
>
> > From: Peter Coppens [mailto:pc.subscriptions@(protected)]
> > Subject: session#getId changes during doGet invocation under
> > heavy load
> >
> > THe problem I run into is that, under heavy load, during the
> > doGet invocation for the login request the session attached
> > to the request is changed by some other thread (the value
> > returned from getId changes and attributes that are originally
> > set are removed).
>
> This is most likely an application problem - storing session- or
> request-specific data in an inappropriately scoped structure (e.g., a
> servlet field). Under light load, this won't hurt, since the insertion
> and retrieval for a given request don't overlap any other requests. As
> the load increases, so does the probability of an overlap and erroneous
> retrieval of data for another request.
>

I can attest to making *this exact mistake* before. A
cut-and-paste-in-haste left a request-scoped variable as a static. It
happened to be the database connection. You can imagine the havoc an error
like this caused.

I also reported a bug against 5.5.12 where in a cluster, the session will
timeout in 2X the session timeout period *regardless* of incoming requests.
Filip has fixed this for 5.5.18+ Could this be your problem?

Tim




---------------------------------------------------------------------
To start a new topic, e-mail: users@(protected)
To unsubscribe, e-mail: users-unsubscribe@(protected)
For additional commands, e-mail: users-help@(protected)