Hi,
We had a similar problem but not due to stress. But, it only happened that
each user would be in one part of our site, switch to another part, and
information from the first part started showing up in the second part. We
know why this occurred, mainly because we have 3 sections to our site..all
identical except each has a particular setting to indicate its not the same.
Because all 3 were identical (we used JSP scriplet code and that special
value to conditionally display information based on that value) they called
the same one JSP page, which in turn called the same one servlet. That
servlet would "get" the object associated with it from the HttpSession if it
existed, otherwise create it. The problem was, when they switched, we didn't
remove the object from the session and they would start getting data from a
previous search or something because the object still existed after they
switched.
Anyways..that does scare me too. I hope its a bug and can be fixed. Sessions
are supposed to be binded to one user each, so there should be no way for
session data in one session to get to another.
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of bradley mclain
> Sent: Tuesday, August 22, 2000 2:50 PM
> To: Orion-Interest
> Subject: request dispatcher problems under load !?!
>
>
> hi all,
>
> we were stress testing our app today with real users
> and found that at high loads some users were winding
> up with others' session info. as we autopopulated
> text controls with previously entered information,
> some users found that info entered by others on other
> client machines was popping into their screens. has
> anyone else seen anything like this before?
>
> the stress on the server was particularly heavy as we
> were running a trace logger at the time, which of
> course involved serious i/o pressure, so this wasn't
> in response to particular user load (about 10 people
> executing fairly involved searches). as soon as we
> shut down the trace function, the problem disappeared,
> but we're worried that once we get 100-200 people at
> once onto this app that we'll have problems again.
>
> we thought that perhaps request dispatcher might be
> the root of the problem. does anyone know if it is
> supposed to be thread safe?
>
> any other ideas?
>
> we're running orion 1.1.37 on redhat linux, using the
> blackdown 1.2.2-RC4 jdk/jre.
>
> thanks,
> bradley mclain
> usmoving.com
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Mail Free email you can access from anywhere!
> http://mail.yahoo.com/
>
