[3116] in java-interest
write on a closed socket
daemon@ATHENA.MIT.EDU (Anselm Baird_smith)
Tue Oct 31 16:32:59 1995
Date: Tue, 31 Oct 1995 20:15:18 +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,
What happens when a server write to some socket that the client has
closed (ie client process is dead) ? From what I can see things seems
to be quiet bad, here is the thread dump I get:
-----
SIGQUIT 3* quit
Full thread dump:
"Thread-15" (TID:0xee3023b8, sys_thread_t:0xef3f0de8) prio=5
"Thread-14" (TID:0xee3005e8, sys_thread_t:0xef420de8) prio=5 *current thread*
java.net.SocketOutputStream.write(SocketOutputStream.java)
java.io.BufferedOutputStream.write(BufferedOutputStream.java)
java.io.PrintStream.write(PrintStream.java)
httpd.Client.loop(Client.java:252)
httpd.Client.run(Client.java:305)
java.lang.Thread.run(Thread.java)
"httpd" (TID:0xee301688, sys_thread_t:0xef450de8) prio=10
java.net.PlainSocketImpl.accept(PlainSocketImpl.java)
java.net.ServerSocket.accept(ServerSocket.java)
httpd.httpd.run(httpd.java:152)
java.lang.Thread.run(Thread.java)
"Event Manager" (TID:0xee301610, sys_thread_t:0xef480de8) prio=9
timers.EventManager.getNextEvent(EventManager.java:198)
timers.EventManager.run(EventManager.java:208)
"Finalizer thread" (TID:0xee300620, sys_thread_t:0xef4d0de8) prio=1
"Async Garbage Collector" (TID:0xee3005d0, sys_thread_t:0xef500de8) prio=1
"Idle thread" (TID:0xee300558, sys_thread_t:0xef530de8) prio=0
"clock handler" (TID:0xee300098, sys_thread_t:0xef5f0de8) prio=11
"main" (TID:0xee300048, sys_thread_t:0x77df0) prio=5
-----
Thread-14 is *in* write, while the other end has closed the socket
(and even disappeared). The application (java) consumes an
tremendous amount of CPU. In brief things are down.
Any hint, sugestion well come.
Anselm.
-
This message was sent to the java-interest mailing list
Info: send 'help' to java-interest-request@java.sun.com
