Remove ElasticsearchInterruptedException and handle interrupt state correctly.
#4712
Assignees
Labels
Comments
ghost
assigned
s1monw
added a commit
to s1monw/elasticsearch
that referenced
this issue
Jan 13, 2014
correctly. InterruptedExceptions should be handled by either rethrowing or restoring the interrupt state (i.e. calling `Thread.currentThread().interrupt()`). This is important since the caller of the is method or subequent method calls might also be interested in this exception. If we ignore the interrupt state the caller might be left unaware of the exception and blocks again on a subsequent method. Closes elastic#4712
brusic
pushed a commit
to brusic/elasticsearch
that referenced
this issue
Jan 19, 2014
correctly. InterruptedExceptions should be handled by either rethrowing or restoring the interrupt state (i.e. calling `Thread.currentThread().interrupt()`). This is important since the caller of the is method or subequent method calls might also be interested in this exception. If we ignore the interrupt state the caller might be left unaware of the exception and blocks again on a subsequent method. Closes elastic#4712
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
InterruptedExceptions should be handled by either rethrowing or restoring the interrupt state (i.e. calling
Thread.currentThread().interrupt()). This is important since the caller of the is method or subequent method calls might also be interested in this exception. If we ignore the interrupt state the caller might be left unaware of the exception and blocks again on a subsequent method.The text was updated successfully, but these errors were encountered: