[
https://issues.apache.org/jira/browse/AMQ-5859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15696988#comment-15696988
]
Aniruddh commented on AMQ-5859:
-------------------------------
Hi All,
I am investigating an issue where in if the Database goes down we get closed
connection errors for transactions through AMQ.
The setup we have is as per below:
Websphere 8557
AMQ 5.10.2
Datastore for message persistence - oracle database
Just would like to know, if this issue talks about the same problem we are
facing?
Any advice will be highly appreciated.
Thanks!
Aniruddh
> Reconnection attempt logic seems wrong in JmsConnector#doInitializeConnection
> -----------------------------------------------------------------------------
>
> Key: AMQ-5859
> URL: https://issues.apache.org/jira/browse/AMQ-5859
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.10.2, 5.11.1
> Reporter: Benoit Wiart
> Priority: Critical
> Fix For: 5.12.0
>
> Attachments:
> 0001-AMQ-5859-Reconnection-attempt-logic-seems-wrong-in-J.patch
>
>
> the reconnection attempts logic based on the reconnection policy seems wrong.
> In JmsConnector#doInitializeConnection the loop trying to reconnect to the
> foreign broker only execute once due to the erroneous test in the while
> {code}
> while (maxRetries < ++attempt && !connectionSerivce.isTerminating());
> {code}
> should be
> {code}
> while (maxRetries > ++attempt && !connectionSerivce.isTerminating());
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
