How to use JmsListener for multicast queue destinations?

Solution Verified - Updated -

Issue

  • When trying to consume a message from a multicast queue, the message goes to the DLQ after several consumption tries.
  • We can see on the broker logs, when having the LoggingActiveMQServerPlugin enabled:
2023-03-23 17:22:31,944 WARN  [org.apache.activemq.artemis.core.server] AMQ222149: Message Reference[270846]:RELIABLE:CoreMessage[messageID=270846,durable=true,userID=null,priority=0, timestamp=Thu Mar 23 17:22:25 EDT 2023,expiration=0, durable=true, address=MYADDRESS1,size=904,properties=TypedProperties[__HDR_dlqDeliveryFailureCause=java.lang.Throwable: Delivery[7] exceeds redelivery policy limit:RedeliveryPolicy {destination = null, collisionAvoidanceFactor = 0.15, maximumRedeliveries = 6, maximumRedeliveryDelay = -1, initialRedeliveryDelay = 1000, useCollisionAvoidance = false, useExponentialBackOff = false, backOffMultiplier = 5.0, redeliveryDelay = 1000, preDispatchCheck = true}, cause:null]]@1438785743 has reached maximum delivery attempts, sending it to Dead Letter Address DLQ from MYQUEUE1

Environment

  • A-MQ 7-x
  • SpringBoot
  • Spring JMS Listener
  • Any valid broker protocol library
    (Openwire, CORE, AMQP, MQTT, STOMP)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content