[infinispan-issues] [JBoss JIRA] (ISPN-2174) CommandAwareRpcDispatcher swallows thread interruptions

[Mircea Markus (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-2174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12752780#comment-12752780 ] 

Mircea Markus commented on ISPN-2174:
-------------------------------------

{quote}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/org/infinispan/remoting/transport/jgroups/CommandAwareRpcDispatcher.java#L421 - 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.
{quote}
- log the fact + throw an InterruptedException
                
> 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: 6.0.0.Final
>
>
> When interruption happens in FutureCollator.getResponseList() method
> see
> https://github.com/infinispan/infinispan/blob/5.1.x/core/src/main/java/org/infinispan/remoting/transport/jgroups/CommandAwareRpcDispatcher.java#L410
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira