[
https://issues.jboss.org/browse/ISPN-2174?page=com.atlassian.jira.plugin....
]
Manik Surtani commented on ISPN-2174:
-------------------------------------
I presume the correct approach should be to check for the interrupted status
(expectedResponses == -1) over here -
https://github.com/infinispan/infinispan/blob/5.1.x/core/src/main/java/or...
- and if we have at least 1 valid response, proceed as normal with that response (the
interrupted flag on the thread should still be set) or if not, log the fact that we were
interrupted before receiving all responses.
CommandAwareRpcDispatcher swallows thread interruptions
-------------------------------------------------------
Key: ISPN-2174
URL:
https://issues.jboss.org/browse/ISPN-2174
Project: Infinispan
Issue Type: Bug
Components: RPC
Affects Versions: 5.1.5.FINAL
Reporter: Michal Linhard
Assignee: Mircea Markus
Labels: jdg, jdg6
Fix For: 5.2.0.ALPHA3, 5.2.0.FINAL
When interruption happens in FutureCollator.getResponseList() method
see
https://github.com/infinispan/infinispan/blob/5.1.x/core/src/main/java/or...
it is ignored and later wrongly dealt with as TimeoutException
(The original exception is not even set as cause anywhere)
This disables possibility of interrupting some cache operations.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira