It's also important to know that WebSphere 3.02 in particular does have
memory leaks, especially if you have security enabled. It's also helpful to
take a look at the memory consumption when your servlet isn't even loaded,
so you can determine if it really has anything to do with your servlet at
all.
Kito D. Mann
Virtua Communications Corp.
[EMAIL PROTECTED]
Tuesday April 11, 2000 02:07 PM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc: (bcc: Kito Mann/PSG/Prudential)
Subject: Re: Servlet Memory Leak
Wouter Boers wrote:
> On 11-Apr-2000 Phil Spencer wrote:
> > I have a WebSphere/OracleThinJDBC configuration. Ad WebSphere is
showing
> > available memory decreasing by about 50K/sec even when there are no
> > active requests to my servlets. I have created no explicit async
processes
> > or threads so I have no idea where this memory is going unless there is
> > a bug in the Oracle drivers.
> >
> > Does anyone have experience with this problem or suggestions how I
might
> > track it down?
>
> This is typical beheviour of a servlet that is looping.
>
> It is certainly not the oracle driver or java. Otherwise my site would
not have
> survived the passed hour ;)
>
> I suggest you check the code for loops that do not stop
I can't speak for Websphere in particular, but it is not at all unusual for
application servers and servlet containers to have background threads
running all
the time, and these background threads can be creating new objects for
temporary
use, just like your servlets can. As just one example, consider the timing
out of
sessions that have been around longer than the inactive interval you
specify. It's
not acceptable to simply wait until the next request (which may never
come), so a
servlet container will generally have a background thread that periodically
looks
through all the active sessions and invalidates the ones that have timed
out.
If you keep watching, you should see the available memory go down to the
threshold
that the garbage collector is using. It will then recycle all the dead
objects,
and available memory should spike up again -- to repeat the pattern of
gradual
use. As long as you get the memory space back, there's no problems.
>
> Wouter
>
Craig McClanahan
___________________________________________________________________________
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
