[jira] [Work logged] (AMQNET-722) Reconnect timing improvements

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

ASF GitHub Bot logged work on AMQNET-722:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 04/Aug/21 09:13
            Start Date: 04/Aug/21 09:13
    Worklog Time Spent: 10m 
      Work Description: michaelandrepearce commented on a change in pull request #69:
URL: https://github.com/apache/activemq-nms-amqp/pull/69#discussion_r682437870



##########
File path: docs/configuration.md
##########
@@ -23,6 +23,7 @@ The options apply to the behavior of the NMS objects such as Connection, Session
 - **nms.requestTimeout** Timeout value that controls how long the client waits on completion of various synchronous interactions, such as opening a producer or consumer, before returning an error. Does not affect synchronous message sends. By default the client will wait indefinitely for a request to complete.
 - **nms.clientIdPrefix** Optional prefix value that is used for generated Client ID values when a new Connection is created for the JMS ConnectionFactory. The default prefix is 'ID:'.
 - **nms.connectionIdPrefix** Optional prefix value that is used for generated Connection ID values when a new Connection is created for the JMS ConnectionFactory. This connection ID is used when logging some information from the JMS Connection object so a configurable prefix can make breadcrumbing the logs easier. The default prefix is 'ID:'.
+- **nms.maxNewConnectionRatePerSec** Allowed approximated rate for how fast connection factory is allowed to create new connection. If there is more request, they will have to wait. Default value is 0 which means unlimited.

Review comment:
       typically -1 means to disable/no limit, can we align please.




-- 
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: gitbox-unsubscribe@activemq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 633382)
    Time Spent: 0.5h  (was: 20m)

> 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: 0.5h
>  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)