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

0

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.

질문됨 2년 전613회 조회
1개 답변
0

Hi,

Apologies for the delay. I was just about to reach out to our MQ team but it seems you have found a solution. Please note that you can also answer your own questions if you have found a solution.

I just want to confirm if upgrading the library fixed all your issues or if there's anything else which needs to be answered?

Hope you have a great day/evening ahead!

AWS
지원 엔지니어
Ryan_A
답변함 2년 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠