How does thread.interrupt() affect a thin driver query?
494125Mar 21 2006 — edited Jun 16 2006I'm looking for information on how connections and queries are affected by a thread interrupt,
particularly on a Solaris box. I'm running a WAS (IBM WebSphere) application using
the jdbc thin driver (9.2.0.7). I have thread1 with an open connection. Other threads
may call thread1.interrupt(). If I am blocked on an query at the time, how does the driver respond? If I am not blocked, is it possible for the connection to get closed?
I couldn't find any info in the JDBC devloper's guide is there any other documentation?
Google search doesn't come up with anything either, so I thought I'd ask the experts.
NOTE: the java.lang.Thread javadoc makes mention about a java.nio ClosedByInterruptException
if you are blocked on a java.nio channel. Since the thin driver uses TCP/IP sockets, I was
wondering if I might get an IOException.