You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Hiram Chirino (JIRA)" <ji...@apache.org> on 2007/10/22 21:38:23 UTC

[jira] Resolved: (AMQ-777) maxReconnectAttempts has no effect

     [ https://issues.apache.org/activemq/browse/AMQ-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hiram Chirino resolved AMQ-777.
-------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 5.2.0)
                   5.0.0

Test case and fix added to trunk in revision 587216.

> maxReconnectAttempts has no effect
> ----------------------------------
>
>                 Key: AMQ-777
>                 URL: https://issues.apache.org/activemq/browse/AMQ-777
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 4.0.1
>            Reporter: Jonny Wray
>            Assignee: Hiram Chirino
>             Fix For: 5.0.0
>
>
> I saw this entry in the forums and I'm having the same problem, setting maxReconnectAttempts to a specific value does not stop the infinite loop of "Waiting for transport to reconnect" from occuring.
> http://www.nabble.com/Discovery-Fail-if-no-Broker-t1824894.html#a4977620
> The forum reply from Hiram Chirino suggests it's a bug but I didn't find an associated JIRA issue.
> Jonny

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.