You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Diego Belfer (JIRA)" <ji...@apache.org> on 2007/10/09 01:56:22 UTC
[jira] Created: (AMQ-1451) FailoverTransport bad handling of
InterruptedException in wait loop.
FailoverTransport bad handling of InterruptedException in wait loop.
--------------------------------------------------------------------
Key: AMQ-1451
URL: https://issues.apache.org/activemq/browse/AMQ-1451
Project: ActiveMQ
Issue Type: Bug
Components: Transport
Affects Versions: 4.1.1
Reporter: Diego Belfer
The forum post http://www.nabble.com/Infinite-loop-if-FailoverTransport-is-interrupted-tf3758516s2354.html#a10799543 refers to this issue.
The InterruptedException should be propagated. In addition, after the thread is interrupted, It starts spinning without waiting because the wait() call is immediately exit due to the Thread.currentThread().interrupt() invoked in the catch block.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-1451) FailoverTransport bad handling of
InterruptedException in wait loop.
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies resolved AMQ-1451.
-----------------------------
Fix Version/s: 5.1.0
Resolution: Fixed
Fixed by svn revision 646354
> FailoverTransport bad handling of InterruptedException in wait loop.
> --------------------------------------------------------------------
>
> Key: AMQ-1451
> URL: https://issues.apache.org/activemq/browse/AMQ-1451
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 4.1.1
> Reporter: Diego Belfer
> Assignee: Rob Davies
> Fix For: 5.1.0
>
>
> The forum post http://www.nabble.com/Infinite-loop-if-FailoverTransport-is-interrupted-tf3758516s2354.html#a10799543 refers to this issue.
> The InterruptedException should be propagated. In addition, after the thread is interrupted, It starts spinning without waiting because the wait() call is immediately exit due to the Thread.currentThread().interrupt() invoked in the catch block.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (AMQ-1451) FailoverTransport bad handling of
InterruptedException in wait loop.
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies reassigned AMQ-1451:
-------------------------------
Assignee: Rob Davies
> FailoverTransport bad handling of InterruptedException in wait loop.
> --------------------------------------------------------------------
>
> Key: AMQ-1451
> URL: https://issues.apache.org/activemq/browse/AMQ-1451
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 4.1.1
> Reporter: Diego Belfer
> Assignee: Rob Davies
> Fix For: 5.1.0
>
>
> The forum post http://www.nabble.com/Infinite-loop-if-FailoverTransport-is-interrupted-tf3758516s2354.html#a10799543 refers to this issue.
> The InterruptedException should be propagated. In addition, after the thread is interrupted, It starts spinning without waiting because the wait() call is immediately exit due to the Thread.currentThread().interrupt() invoked in the catch block.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.