[
https://issues.apache.org/jira/browse/ARTEMIS-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17886507#comment-17886507
]
ASF subversion and git services commented on ARTEMIS-5085:
----------------------------------------------------------
Commit 8a1f9e8874d4f4fb175c558fa737b30cde172218 in activemq-artemis's branch
refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=8a1f9e8874 ]
ARTEMIS-5085 use retry parameters on initial connection
When the Core client attempts to create the initial connection to a
broker when initialConnectAttempts > 1 it will adhere to retryInterval,
but it will ignore retryIntervalMultiplier & maxRetryInterval. This
commit fixes that so that these parameters are taken into account.
> Use retry parameters on initial connection
> ------------------------------------------
>
> Key: ARTEMIS-5085
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5085
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
>
> Currently the {{retryInterval}} is applied when attempting the initial
> connection from the Core client to the broker. However,
> {{retryIntervalMultiplier}} and {{maxRetryInterval}} are not. These
> parameters are only applied to reconnect attempts. Both
> {{retryIntervalMultiplier}} and {{maxRetryInterval}} should be applied to the
> initial connection just like {{retryInterval}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
