-----------------------------
Please read the FAQ!
<http://java.apache.org/faq/>
-----------------------------
> Just finished reading the column Straight Talking by Alan
> Williamson and he
> mentions an issue he found working with
> both a Linux and Sun implementation of Java 2.
> If you are spawning threads and not calling Thread.stop() the count of
> active threads climbs indefinately.
> Only Thread.stop() actually frees the thread. ( Despite being a deprecated
> method).
> See the Java Developer's Journal July 1999.
>
> I haven't peeked at the JServ source for this yet, but was curious if this
> had ever been an issue since it seems that this project would
> likely suffer from it.
God I hate being misquoted! It was nothing to do with Java2 that we
noticed the problem, it was with Java1.1.x. My comment about Java2 was
that it was deprecated, the stop(), method that is, and I was merely
wondering if it suffered from the same problem.
One thing I will say, is that between soft-restarts, ie where the JServ
loads new instance of classes, the thread count does indeed keep getting
bigger. But JWS suffers from this also, so its not a JServ specific
problem.
Alan
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
