What are you using to determine whether the VM has released the memory? You
should notice a difference if you call RunTime.getRuntime().freeMemory(),
but you will not normally see a difference in the NT Memory Meter. This is
because, garbage collection returns the released memory to the VM's heap,
not the operating system.
(*Chris*)
----- Original Message -----
From: Prasad Akella <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 23, 1999 11:02 AM
Subject: JRun Memory usage -- Session Data
> Hi,
>
> Using JRun 2.3.3 on Windows NT.
>
> When a user logs in, some user data is being stored in the session (using
> 'putValue') and when the logs out, explicitly calling 'remomeValue' and
then
> invalidating the session. Even included an explicit call to the garbage
> collection. But the memory doesn't seem to be released. (Even waiting for
> sometime for the 'garbage collection to happen' didn't help)
>
> Shouldn't the Servlet Engine release all the memory associated with a
> session once the session is invalidated?
> Can we force 'gc' to happen? Any body has any clue?
>
> Prasad
>
>
___________________________________________________________________________
> 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
>
___________________________________________________________________________
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
