First
of all..are you releasing the reference to the EJB? If not, how is it that each
time you call the page some more memory is used? It sounds like something is
being referenced on each request, but not being set to null or is not falling
out of scope (request scope or method scope). Secondly, keep in mind that the GC
does not run immediately. Its a low priority thread and may not clear up memory
until its needed. Therefore, if you want to force it, try System.gc() or
Runtime.gc() to see if that helps. It won't force it, but it will tell the
system to try to have the thread run now (instead of later) if the JVM will alot
time for it.
-----Original Message-----
From: Dan DiCesare [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 23, 2001 11:59 AM
To: Orion-Interest
Subject: Memory LeakHello,
I am using JSP <useBean> tags to invoke java beans. In my java beans I create a reference to my EJB's. In my JSP I scope the bean as session. In other words the syntax looks as follows:
<jsp:useBean id="fooBean" scope="session" class="FooBean" />
What we are noticing is that every time the page is called, a certain amount of memory is used by each session as expected by the session scope. However, when the session is complete, the memory is not released by the JVM. The end result is that we need to stop Orion server and restart to clear the JVM memory usage. Can anyone advise as to what we need to do.
Thanks
-Dan
Get your FREE download of MSN Explorer at http://explorer.msn.com
