activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mohan Kishore (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AMQ-2047) FanoutTransport does not honor the initialReconnectDelay
Date Tue, 30 Dec 2008 00:25:05 GMT

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

Mohan Kishore updated AMQ-2047:
-------------------------------

    Attachment: patch.txt

patch against 5.1 class - basically pushes the "post successful connect" code a little lower
in the code - until after the "restoreTransport()" call.

Also ensures that the "initialReconnectDelay" parameter is honored after a reconnect.

> 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
>         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