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

well, before submitting issue, I'd like to ask if there's already a possibility to configure that way. ok, got your point, will open a request 2018-04-04 17:29 GMT+05:00 Tim Bain : > If you think that message expiration should be checked when the publisher > publishes the

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

If you think that message expiration should be checked when the publisher publishes the message, you can submit an enhancement request in JIRA for it. Tim On Tue, Apr 3, 2018, 11:15 PM Илья Шипицин wrote: > Tim, thank you for your investigation (looks like our client is

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

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

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,