[
https://issues.apache.org/jira/browse/AMQNET-722?focusedWorklogId=623535&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-623535
]
ASF GitHub Bot logged work on AMQNET-722:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 16/Jul/21 10:55
Start Date: 16/Jul/21 10:55
Worklog Time Spent: 10m
Work Description: lukeabsent opened a new pull request #69:
URL: https://github.com/apache/activemq-nms-amqp/pull/69
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 623535)
Remaining Estimate: 0h
Time Spent: 10m
> 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: 10m
> 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)
