expired messages --> DLQ ? (when expiration=0)

hello, activemq.log:2018-04-03 10:42:57,961 | INFO | preProcessDispatch: MessageDispatch {commandId = 0, responseRequired = false, consumerId = ID:dd-amq-app01. sd.kontur.ru-32887-1522738593874-4:1:1:1, destination = queue://DLQ.EdiInbound, message = ActiveMQTextMessage {commandId = 5,

Re: Older Message Not Consumed(Stay Untouched in queue) Newer Messages consumed

No - we weren’t using selectors. The only “special” feature we were using was Virtual Topics - we saw the order shuffled on the queues created for the Virtual Topic Consumers. > On Apr 2, 2018, at 11:20 PM, Tim Bain wrote: > > @RuralHunter, same question as to the OP:

Re: Older Message Not Consumed(Stay Untouched in queue) Newer Messages consumed

When you say "shuffled", do you simply mean that the message went to the back of the queue when it got sent back for broker-side redelivery? Or do you mean that actual randomization of all messages on the queue occurred? Tim On Tue, Apr 3, 2018 at 8:29 AM, Quinn Stevenson

Re: expired messages --> DLQ ? (when expiration=0)

Ilya, The output you're seeing is from the message as it's being put onto the DLQ. (destination=queue://DLQ.EdiInbound") This means that it has already passed through the set of transformations that occur in orc.apache.activemq.broker.region.RegionBroker.sendToDeadLetterQueue() and

Re: expired messages --> DLQ ? (when expiration=0)

Tim, thank you for your investigation (looks like our client is buggy, we'll look at it). besides that, doesn't it look strange, accept message and drop it right away ? is there a possibility to reject such messages ? it will inform client in a better way 2018-04-04 9:12 GMT+05:00 Tim Bain