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

Posted to issues@activemq.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/04/25 18:00:00 UTC

[jira] [Commented] (AMQNET-722) Reconnect timing improvements

    [ https://issues.apache.org/jira/browse/AMQNET-722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17527684#comment-17527684 ] 

ASF subversion and git services commented on AMQNET-722:
--------------------------------------------------------

Commit ba3f5760a21a9bcc0ae8053e2cc2e02d0f9ac448 in activemq-nms-amqp's branch refs/heads/main from lukeabsent
[ https://gitbox.apache.org/repos/asf?p=activemq-nms-amqp.git;h=ba3f576 ]

AMQNET-722 Updated config doc, and little update to random delay time


> Reconnect timing improvements
> -----------------------------
>
>                 Key: AMQNET-722
>                 URL: https://issues.apache.org/jira/browse/AMQNET-722
>             Project: ActiveMQ .Net
>          Issue Type: New Feature
>          Components: AMQP, NMS
>            Reporter: lukeabsent
>            Priority: Major
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Reconnect backoff time randomisation. In case of broker global disconect, to avoid all client connecting again at the very same moment. It would be good to have some randomisation in retry time, configurable.
> Also, clients could have their own logic of reconnect that could cause lot of reconnect. It would be good to have ability to limit the rate of new connection creation, configurable.
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.7#820007)