Use of ACTIVE/STANDBY ActiveMQ results in "supressing duplicate delivery on connection" errors when used with the redelivery plugin

When connecting to the active broker ActiveMQ via JMS in java without a failure url (e.g. ssl://broker_address), the activeMQ redelivery plugin works as expected, i.e retries X times before moving to the DLQ.

When copying the Java failover string from the AWS MQ console ( failover:(ssl://broker1:61617,ssl://broker2:61617), and using that to connect, the re-delivery plugin no longer functions as expected. The scheduler runs, and messages are infact re-dispatched, but the the activeMQ java consumer throws an exception, stating "suppressing duplicate delivery on connection".

Note everything else remained constant between testing with a failure url and testing without the failure url.

Version of ActiveMQ being used is 5.16.3.

The first thing I want to ask, is anyone using redelivery plugin with failover strings successfully?

Secondly, anyone have the specific issue I've faced and can suggest any solutions?

=====SOLUTION======= This ended up being a problem with the default client library for activemq with springboot, upgrading the activemq library to 5.16.3 fixed this bug.