hendre wrote:No need for such snotty behavior; might there be a SLIGHT chance you misunderstand intentions?
I bow to your superior knowledge my lord!
However this is my understanding of thread interruption: Calling interrupt does not necessarily stop the target thread from doing what it is doing; it merely delivers the message that interruption has been requested.You certainly read the javadocs correctly.
If I dot not explicitly know (as in have the source) if a third party blocking method handles interruption correctly, how can I be sure that it will interrupt each time I call interrupt and how can I be sure what the duration will be before the thread is interrupted.you have just proven it to yourself. And because it worked this time, the next times you deal with the same API, framework and/or service you'll reliably get the same results. When you connect through a different API, framework or service you'll have to test it again of course, but I have faith in your abilities as a developer to reason that for yourself.
Calling interrupt is by no means a guarantee that a thread will stop its execution.No, but my point was and is that in this particular case that you are describing you do have that guarantee, under the assumption that there are no other breaking points in your thread code. Until someone changes something, but you cannot really defend against that through code.
My faith in Java is a strong as ever though!I would have more faith in your own intelligence and reasoning skills. Java is only a tool you can use to do great or terrible things.