Peter Delahunty wrote:
>
> I should imagine that it is something to do with the garbage collection. As
> far as i know session objects use the least used must die algorithim.
> Therefore session objects created earlier (and therefore least used) must
> make way for new ones.
This can't be, because the container has to manage references to session
objects till the timeout interval (or explicit invalidation).
> However if max number of sessions is 40000 and you are creating only 50 then
> it could be something else.
Possibly!
>
> Hello,
> I am testing my application with a tool which simulates 50 concurrent
> access. When 50 people bang into the application the sessions that were
> created are lost.
> Jrun has no problem getting new sessions. Its only that it kills the
> earlier sessions.
> The session settings in the Jrun are :
>
> Max number of Sessions :40000
> Session Invalidation time : 900000 (15min)
> Session Invalidation interval : 10000 (10sec)
>
Regards,
Subrahmanyam
------------------------------------------------
A.V.B. Subrahmanyam//http://www.Subrahmanyam.com
------------------------------------------------
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
