You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Mohan Kishore (JIRA)" <ji...@apache.org> on 2008/12/30 01:21:05 UTC
[jira] Created: (AMQ-2047) FanoutTransport does not honor the
initialReconnectDelay
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.2.0, 5.1.0
Reporter: Mohan Kishore
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.
[jira] Updated: (AMQ-2047) FanoutTransport does not honor the
initialReconnectDelay
Posted by "Mohan Kishore (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (AMQ-2047) FanoutTransport does not honor the
initialReconnectDelay
Posted by "Dejan Bosanac (JIRA)" <ji...@apache.org>.
[ 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.