[3349] in java-interest
interrupting a read()ing thread
daemon@ATHENA.MIT.EDU (Anselm Baird_smith)
Wed Nov 8 15:49:12 1995
Date: Wed, 8 Nov 1995 16:49:36 +0100
From: Anselm Baird_smith <Anselm.Baird_Smith@inria.fr>
To: java-interest@java.sun.com
Reply-To: Anselm Baird-Smith <Anselm.BairdSmith@inria.fr>
Hi,
[Using JDK-beta: 4569726 Nov 2 17:42 JDK-beta-solaris2-sparc.tar.Z]
I am still struggling with this problem. Here is what I am doing,
after a lot of testing:
thread-1: read() on the socket
thread-2: . closes the socket (behind the scene)
. stops thread-1 through thread.stop()
. remove all refs to thread-1 (i.e thread-1 = null)
The socket gets closed "properly" - if I believe netstat - but the
read()ing thread exists, and never gets killed (although it is reading
on a closed socket). Should this be considered a Java bug ? Is there
any other solution (other than turning back to the old ages C) ? I
just cannot live with those zombie threads.
Thanks,
Anselm.
-
This message was sent to the java-interest mailing list
Info: send 'help' to java-interest-request@java.sun.com
