[
https://issues.apache.org/jira/browse/ARTEMIS-4460?focusedWorklogId=885376&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-885376
]
ASF GitHub Bot logged work on ARTEMIS-4460:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 16/Oct/23 13:35
Start Date: 16/Oct/23 13:35
Worklog Time Spent: 10m
Work Description: AntonRoskvist opened a new pull request, #4649:
URL: https://github.com/apache/activemq-artemis/pull/4649
…tible versions
Client will now try to downgrade version incrementally until it finds some
version the broker accepts.
Also added two minor fixes found during troubleshooting:
one for recreating producers on the broker,
one for adding packets sent during the communications lock to the resend
cache to get rid of an ugly WARN message (AMQ212036)
These fixes are also covered by added tests.
Hope everything looks good, just let me know otherwise
Issue Time Tracking
-------------------
Worklog Id: (was: 885376)
Remaining Estimate: 0h
Time Spent: 10m
> Core client reconnect/failover loop because of incompatible versions
> --------------------------------------------------------------------
>
> Key: ARTEMIS-4460
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4460
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Anton Roskvist
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If reconnecting or running failover to a broker that is not compatible with
> the current client version an infinite reconnect/failover loop can occur
> (even if setting max retry/reconnect/failoverattempts to some finite value).
> This can be triggered by a broker upgrade followed by a rollback for example.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
