activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dejan Bosanac (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQ-2047) FanoutTransport does not honor the initialReconnectDelay
Date Thu, 15 Jan 2009 18:01:03 GMT

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

Dejan Bosanac resolved AMQ-2047.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 5.3.0
         Assignee: Dejan Bosanac

Committed in the SVN revision 734766. Thanks for the fix

> FanoutTransport does not honor the initialReconnectDelay
> --------------------------------------------------------
>
>                 Key: AMQ-2047
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2047
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.1.0, 5.2.0
>            Reporter: Mohan Kishore
>            Assignee: Dejan Bosanac
>             Fix For: 5.3.0
>
>         Attachments: patch.txt
>
>
> The TransportHandler does not honor the passed in "initialReconnectDelay" parameter.
It has a hard-coded value of "10" milliseconds.
> Would also like to point out that the code seems to assume that the child transport has
been created successfully as soon as the "TransportFactory.compositeConnect()" returns. During
runtime, if a given node is down, the exception is actually thrown a little further down the
code - when the "restoreTransport()" method is called.

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


Mime
View raw message