You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/09/30 12:42:04 UTC

[jira] [Commented] (AMQ-5951) failover maxReconnect=0 url can block on reconnect

    [ https://issues.apache.org/jira/browse/AMQ-5951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936692#comment-14936692 ] 

ASF subversion and git services commented on AMQ-5951:
------------------------------------------------------

Commit 8514e38135cf3c4da913806f3677a89785613e10 in activemq's branch refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=8514e38 ]

https://issues.apache.org/jira/browse/AMQ-5951 - scenario wheere transaction command can block, additional test and further fix


> failover maxReconnect=0 url can block on reconnect
> --------------------------------------------------
>
>                 Key: AMQ-5951
>                 URL: https://issues.apache.org/jira/browse/AMQ-5951
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client
>    Affects Versions: 5.12.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.12.1, 5.13.0
>
>
> client with {code}failover:(tcp://localhost:61616)?maxReconnectAttempts=0{code}
> with exception listener that attempts to use the connection, ie: do a rollback/ack/shutdown, can block pending transport close.
> A retrying failover oneway send will block the mutex transport in error.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)