on 12/1/2000 8:06 AM, "Nissim Karpenstein" <[EMAIL PROTECTED]> wrote:
> I use the same driver (but we have the 20 user version), and I have seen
> that same thing happen. I guess that when tomcat reloads a class, the
> connections in the pool don't get garbage collected for some reason.
>
> Does anyone have any suggestions on how to go about debugging this?
>
> -Nissim
There are some JVM's (I don't know which) that do leak memory as a result of
classreloading. Here is a posting from a guy about this exact fact (I can't
reveal who wrote this...sorry...)
> Most JDK's that I know of still have severe problems with garbage collecting
> classes. Add to that the other problems associated with dumping and reloading
> classes, and you have the recipe for nightmare on elm street.
>
> The problem is that instead of developing good deployment and development
> strategies, Servlet and JSP developers will think this is an okay way to do
> things, and then complain bitterly when their VM's leak memory and have to be
> re-booted every other day, and get trapped in a web of twisty casts.
>
> Sorry, but I know that it's a nice development feature, but it's a damn
> dangerous way to deal with deployed systems.
-jon
--
twice of not very much is still a lot more than not very much
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
