-----------------------------
Please read the FAQ!
<http://java.apache.org/faq/>
-----------------------------
Actually, the WClient class extends thread, which is odd since it
is not a thread (hey...I didn't write that code...honest). I only
noticed it because I went back to look at the class to make sure
that it wasn't after I read you're note.
I was also having memory problems because of an open socket and
datastreams which I fixed, but have been confused as to why
OptimizeIt was insisting that jserv was hanging on to instances
of WClient even though I was dumping out info from the servlet
that said the reference was null (along with a thread for each
instance).
Thanks, I'll bet that is the problem.
Cary
-----Original Message-----
From: Stefan Mainz [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 30, 1999 1:18 AM
To: Java Apache Users
Subject: Re: servlet thread not going away
Some thougths:
- is WClient starting a new thread, which is not terminated ?
- does WClient free all System resources (Sockets, ...) ?
Stefan
--
--------------------------------------------------------------
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]
--
--------------------------------------------------------------
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]
