In a Java client application connecting to an AMQ server, the retryIntervalMultiplier parameter appears to be ignored during initial connection attempts. Although retryInterval is correctly applied to both initial and reconnect attempts. However retryInterval is working even though both the Support Team and SME in an email thread say that retryInterval, retryIntervalMultiplier, and maxRetryInterval   should only work on reconnect attempts and not initial attempts, however retryInterval actually does work as expected during initial connection attempts.  Customer would like clarification on this for their new project, and would like for retryIntervalMultiplier to also work on initial connection attempts: The Customer relies heavily on our messaging system and are now moving to OpenShift. They may have outages for various reasons and find that the parameter retryIntervalMultiplier on initial connection attempts would be extremely useful in their case.

On the linked case you can find a reproducer, however in this case the connection string is:

tcp://localhost:61616?initialConnectAttempts=7&retryInterval=2000&retryIntervalMultiplier=5.0&maxRetryInterval=600000

Customer has tried multiple versions of the client library including the latest

<dependency>
   <groupId>org.apache.activemq</groupId>
   <artifactId>artemis-jms-client</artifactId>
   <version>2.33.0.redhat-00015</version>
</dependency>

1. Is this a documentation issue?
2. Why does the retryInterval work on initial connection attempts also even though it is stated that it should work on reconnect attempts only?
3. Is it possible to have retryIntervalMultiplier available for initial connection attempts just as retryInterval?