[
https://issues.apache.org/jira/browse/AMQNET-722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408702#comment-17408702
]
ASF subversion and git services commented on AMQNET-722:
--------------------------------------------------------
Commit 34d9df006373262e77f6648051a54b92b47969d7 in activemq-nms-amqp's branch
refs/heads/2.0.x from lukeabsent
[ https://gitbox.apache.org/repos/asf?p=activemq-nms-amqp.git;h=34d9df0 ]
AMQNET-722 Connection timing new options
> 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.3.4#803005)
