To kill a connection (and the thread running it)

Question

As a last resort to deal with potential hanging in the DB (Sybase), I'd like to
find a way to stop the processing. I'm willing to violate some rule, such as calling
Thread.stop. But that doesn't seem to drop the connection. Any suggestion how
I can drop that connection? Thanks. /Bill

Answer 1

Joe, as you know I also posted at Sybase/jdbc. I'm reposting the last post here
for the benefits of anyone else might be interested in the thread.
I tried out cancel and it essentially did the same thing as set timeout, except
the time is more precise since the application controls it. Set timeout is more
economical to operate though. I'll probably take one of these, which do solve
half of the problem, for the time being until something better comes along. Unfortunately,
though, the other half causes more problems because when that happens, other executions
will pile on and get blocked as well.
Joseph Weinstein <[email protected]> wrote:
>
>
Bill wrote:
As a last resort to deal with potential hanging in the DB (Sybase),I'd like to
find a way to stop the processing. I'm willing to violate some rule,such as calling
Thread.stop. But that doesn't seem to drop the connection. Any suggestionhow
I can drop that connection? Thanks. /BillKilling the thread is bad for the server, because it only creates a fixed
number of
execute-threads to do user work... The things you should try are:
1 - Call cancel() on the jdbc statement that is hanging. Call connection.close()
on the connection. This requires having access to those objects from
another
thread.
2 - Find out the spid of the hung DBMS session (either record it ahead
of time or
query the DBMS with another connection) and use T-SQL to kill that DBMS
session.
3 - Try resetting the pool.
Joe