From: Starer, Steve (sstarer@fahnestock.com)
Date: Fri May 23 2003 - 09:13:47 EDT
Gurus,
We recently implemented a thread server to replace a process based server. A
client program used to connect to a server, which forked a process to handle
the work, then went merrily back to listening on the port it uses. If
something went awry with that users work, I could kill the process the
client connected to, and that would be that. Now our app still listens on
the same port, but when a client makes a connection, instead of forking a
new process, the server spawns a thread to handle the interaction.
It's a new model for us, and while it's not without a couple of teething
pains, it's mostly working just fine. But yesterday we had an issue where a
thread was blocking on something, and gummed up the works for everyone.
Now, I can't kill the process without knocking everybody off the box. The
developer asked me if I knew of a way to close down the connection at the
network level. I asked the developer if he could kill the thread, but he
said that's not implemented yet.
I have two questions you all might be able to assist with...
Is there a way to administratively force a change in the state if an IP
connection from ESTABLISHED from the command line?
Such as below
10.125.1.100.5500 10.125.14.200.3199 8760 0 24820 0
ESTABLISHED
That would terminate the thread using that particular connection
Is there a way for me to administratively kill a thread running in an lwp
under my server? Like a kill (-9) <pid>
I will summarize...
Thanks all, and have a great weekend!
regards,
Steve Starer
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:26:28 EDT