Parambir,
I'm copying your email to the dev list. You should send all questions to
one of the lists so that a) you get more people thinking about your
problem, and b) other people can learn from the solution.
On Thu, 26 Feb 2004, Parambir Gill wrote:
> I am running a process in a Thread. This process accesses the DB
> through Proxool. If i call Thread.interrupt() on this thread, I
> get the following error:
>
> 1241365 [Thread-9] ERROR proxool.AbstractProxyConnection - Unable
> to acquire write lock for status
Our concurrent locking code (from Doug Lea) can throw an
InterruptedException and we are incorrectly assuming that this exception
originates from that code. That is it a bug.
> The thread does NOT get interrupted.
> We are using Proxool.0.8.2
>
> Could you provide any suggestions? How would I interrupt the Thread
> without this error?
Not sure. Nobody has ever asked to do that before. What sort of behaviour
would you expect?
I suppose that if we spot the difference between InterruptedExceptions
that occur in the lock code and those originating from elsewhere we can
just throw the InterruptedException when approriate.
- Bill
|
