That may be a bit to simple, as this is just performing one
request after the other. You may have to force concurrent
request:
i=1
while [ $i -lt 20000 ] ; do
j=1
while [ $j -lt 10 ] ; do
# start lynx in background
lynx -source $URL > /dev/null &
j=`expr $j + 1`
done
wait # until all background tasks returned
i=`expr $i + 1`
done
You may also have a look at ab or jMeter.
They allow for a better test than home grown test like yours.
(My enhancement might not help much, as the result of the script
depends to a degree on the time that lynx needs to start.)
> -----Original Message-----
> From: Joseph Shraibman [mailto:[EMAIL PROTECTED]
> Sent: Thursday, March 18, 2004 8:32 PM
> To: Tomcat Users List
> Subject: Re: Horrible memory leak in tomcat 5.0.19 (JMX bug?)
>
>
> My test to try to reproduce this bug was:
> i=1
> while [ $i -lt 20000 ] ; do
> lynx -source $URL > /dev/null
> i=`expr $i + 1`
> done
>
> ... where I changed $URL to point to different servlets or jsps.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
