You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Jeff Genender (Created) (JIRA)" <ji...@apache.org> on 2011/09/28 01:30:45 UTC
[jira] [Created] (AMQ-3513) initialReconnectDelay is ignored for
Failover transport
initialReconnectDelay is ignored for Failover transport
-------------------------------------------------------
Key: AMQ-3513
URL: https://issues.apache.org/jira/browse/AMQ-3513
Project: ActiveMQ
Issue Type: Bug
Components: Transport
Affects Versions: 5.5.0
Reporter: Jeff Genender
initalReconnectDelay is ignored during failover. If multiple brokers are running, the failover transport attempts to failover immediately and does not honor the initialReconnect delay. Patch is attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3513) initialReconnectDelay is ignored for
Failover transport
Posted by "Timothy Bish (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116022#comment-13116022 ]
Timothy Bish commented on AMQ-3513:
-----------------------------------
Pretty sure bad things will happen if the initalReconnectDelay is set to zero using this patch.
> initialReconnectDelay is ignored for Failover transport
> -------------------------------------------------------
>
> Key: AMQ-3513
> URL: https://issues.apache.org/jira/browse/AMQ-3513
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.5.0
> Reporter: Jeff Genender
> Attachments: AMQ-3513.patch
>
>
> initalReconnectDelay is ignored during failover. If multiple brokers are running, the failover transport attempts to failover immediately and does not honor the initialReconnect delay. Patch is attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-3513) initialReconnectDelay is ignored for
Failover transport
Posted by "Jeff Genender (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Genender updated AMQ-3513:
-------------------------------
Attachment: AMQ-3513-take2.patch
> initialReconnectDelay is ignored for Failover transport
> -------------------------------------------------------
>
> Key: AMQ-3513
> URL: https://issues.apache.org/jira/browse/AMQ-3513
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.5.0
> Reporter: Jeff Genender
> Attachments: AMQ-3513-take2.patch, AMQ-3513.patch
>
>
> initalReconnectDelay is ignored during failover. If multiple brokers are running, the failover transport attempts to failover immediately and does not honor the initialReconnect delay. Patch is attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-3513) initialReconnectDelay is ignored for
Failover transport
Posted by "Jeff Genender (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Genender updated AMQ-3513:
-------------------------------
Attachment: AMQ-3513-take3.patch
Patch take 3... I moved the delay above the while loop, so it really is just an initial reconnect and not on every connection.
> initialReconnectDelay is ignored for Failover transport
> -------------------------------------------------------
>
> Key: AMQ-3513
> URL: https://issues.apache.org/jira/browse/AMQ-3513
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.5.0
> Reporter: Jeff Genender
> Attachments: AMQ-3513-take2.patch, AMQ-3513-take3.patch, AMQ-3513.patch
>
>
> initalReconnectDelay is ignored during failover. If multiple brokers are running, the failover transport attempts to failover immediately and does not honor the initialReconnect delay. Patch is attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3513) initialReconnectDelay is ignored for
Failover transport
Posted by "Jeff Genender (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116027#comment-13116027 ]
Jeff Genender commented on AMQ-3513:
------------------------------------
Ah right... 0 == forever... ok... fixed it with a guard. All works now.
> initialReconnectDelay is ignored for Failover transport
> -------------------------------------------------------
>
> Key: AMQ-3513
> URL: https://issues.apache.org/jira/browse/AMQ-3513
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.5.0
> Reporter: Jeff Genender
> Attachments: AMQ-3513-take2.patch, AMQ-3513.patch
>
>
> initalReconnectDelay is ignored during failover. If multiple brokers are running, the failover transport attempts to failover immediately and does not honor the initialReconnect delay. Patch is attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3513) initialReconnectDelay is ignored for
Failover transport
Posted by "Jeff Genender (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116028#comment-13116028 ]
Jeff Genender commented on AMQ-3513:
------------------------------------
AMQ-3513-take2.patch is attached with the guard.
> initialReconnectDelay is ignored for Failover transport
> -------------------------------------------------------
>
> Key: AMQ-3513
> URL: https://issues.apache.org/jira/browse/AMQ-3513
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.5.0
> Reporter: Jeff Genender
> Attachments: AMQ-3513-take2.patch, AMQ-3513.patch
>
>
> initalReconnectDelay is ignored during failover. If multiple brokers are running, the failover transport attempts to failover immediately and does not honor the initialReconnect delay. Patch is attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AMQ-3513) initialReconnectDelay is ignored for
Failover transport
Posted by "Timothy Bish (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQ-3513.
-------------------------------
Resolution: Fixed
Fix Version/s: 5.6.0
Patch applied in trunk.
> initialReconnectDelay is ignored for Failover transport
> -------------------------------------------------------
>
> Key: AMQ-3513
> URL: https://issues.apache.org/jira/browse/AMQ-3513
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.5.0
> Reporter: Jeff Genender
> Fix For: 5.6.0
>
> Attachments: AMQ-3513-take2.patch, AMQ-3513-take3.patch, AMQ-3513.patch
>
>
> initalReconnectDelay is ignored during failover. If multiple brokers are running, the failover transport attempts to failover immediately and does not honor the initialReconnect delay. Patch is attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-3513) initialReconnectDelay is ignored for
Failover transport
Posted by "Jeff Genender (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Genender updated AMQ-3513:
-------------------------------
Attachment: AMQ-3513.patch
> initialReconnectDelay is ignored for Failover transport
> -------------------------------------------------------
>
> Key: AMQ-3513
> URL: https://issues.apache.org/jira/browse/AMQ-3513
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.5.0
> Reporter: Jeff Genender
> Attachments: AMQ-3513.patch
>
>
> initalReconnectDelay is ignored during failover. If multiple brokers are running, the failover transport attempts to failover immediately and does not honor the initialReconnect delay. Patch is attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira