You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Ben Nisbet (JIRA)" <ji...@apache.org> on 2016/04/29 18:15:12 UTC
[jira] [Updated] (AMQ-6273) ReconnectionPolicy.getNextDelay(int
attempt) always returns zero when
maxReconnectAttempts/maxInitialConnectAttempts ==
ReconnectionPolicy.INFINITE
[ https://issues.apache.org/jira/browse/AMQ-6273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ben Nisbet updated AMQ-6273:
----------------------------
Summary: ReconnectionPolicy.getNextDelay(int attempt) always returns zero when maxReconnectAttempts/maxInitialConnectAttempts == ReconnectionPolicy.INFINITE (was: ReconnectionPolicy.getNextDelay(int attempt) always returns zero when maxSendRetries == ReconnectionPolicy.INFINITE)
> ReconnectionPolicy.getNextDelay(int attempt) always returns zero when maxReconnectAttempts/maxInitialConnectAttempts == ReconnectionPolicy.INFINITE
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-6273
> URL: https://issues.apache.org/jira/browse/AMQ-6273
> Project: ActiveMQ
> Issue Type: Bug
> Components: Connector
> Affects Versions: NEEDS_REVIEW, 5.12.1
> Environment: WebLogic 10.3.6, HotSpot JDK 1.7
> Reporter: Ben Nisbet
>
> The v.5.12.1 release of class org.apache.activemq.network.jms.JmsConnector contains a defect within method *private void doInitializeConnection(boolean local) throws Exception* that causes the *attempt* variable to
> always retain a value of zero if ReconnectionPolicy.maxSendRetries == ReconnectionPolicy.INFINITE. (irrespective of the actual number of loop iterations)
> This indirectly prevents the connector from using any of the following ReconnectionPolicy configuration properties:
> private long initialReconnectDelay = 1000L;
> private long maximumReconnectDelay = 30000;
> private boolean useExponentialBackOff = false;
> private double backOffMultiplier = 2.0;
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)