Re: [Proxool-developer] Re: Error due to Interruption of Thread

[Jean-Henry B. <ber...@ne...>]

bi...@lo... wrote:

>  
>
>>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
>  
>
I guess Throwable.getCause() can be very handy in a case like this.
(make sure the lock code initializes the "cause" and when checking, if
the cause is different, even if it was not initialized - i.e. null - it 
would mean
it's not generated by the locking code).
Alas all this depends on the platform version , since the "cause"
handling is only available since version 1.4.

Jean