[jboss-jira] [JBoss JIRA] Resolved: (JGRP-1004) GroupRequest: don't ignore InterruptedException

[Bela Ban (JIRA)]

     [ https://jira.jboss.org/jira/browse/JGRP-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bela Ban resolved JGRP-1004.
----------------------------

    Resolution: Done


> GroupRequest: don't ignore InterruptedException
> -----------------------------------------------
>
>                 Key: JGRP-1004
>                 URL: https://jira.jboss.org/jira/browse/JGRP-1004
>             Project: JGroups
>          Issue Type: Task
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>            Priority: Minor
>             Fix For: 2.6.11, 2.8
>
>
> [Mircea]
> This is related to https://jira.jboss.org/jira/browse/ISPN-38 (Early distributed deadlock detection).
> When I determine that a deadlock scenario happens, I try to interrupt a tx originated locally. This translates to an thread.interrupt() call on a thread that is replicating to other caches. The issue is that this call is ignored in jgroups's GroupRequest:
>    private boolean collectResponses(long timeout)  {
>                .....
>                if(timeout > 0) {
>                    try {
>                        completed.await(timeout, TimeUnit.MILLISECONDS); //LINE 552
>                    }
>                    catch(Exception e) {
>                    }
>                }
>                ....
>   }
> So my call to interrupt is ignored (line 552) and the collectResponses method will only return after timeout elapses - not good for me, as I want the method to return immediately if thread is interrupted.
> Would it be possible to enhance the code to be aware of interrupt calls? This is in JGroups 2.8.0 Beta2. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira