Update on my Servlet Memory Leak problem...
The problem really turned out to be the Oracle JDBC drivers.
The 50K/second perceived leak was a 'red herring' - it is
the memory consumed by the WebSphere monitoring tool. With
the original (actually the latest available from the Oracle
website) drivers, garbage collection seems to be disabled
so this 50K/sec shows up as monotonically decreasing available
memory until my 0.5 Gig heap is consumed!
I reinstalled some earlier JDBC drivers and memory usage levels
out at about 3Mb.
Many thanks to all those who replied, I hope the above info
is of use to others.
Phil
--
Phil Spencer
[EMAIL PROTECTED]
-----Original Message-----
From: Phil z.h.x.f.p. Spencer
Sent: Tuesday, April 11, 2000 2:31 PM
To: SERVLET-INTEREST
Subject: UNAUTHENTICATED: Servlet Memory Leak
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?
___________________________________________________________________________
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
