mattrpav commented on PR #1286: URL: https://github.com/apache/activemq/pull/1286#issuecomment-2307393555
@cshannon the updated test has the full repro scenario. The issue comes down to: 1. Should a browser send a poison ack if the message redeliveryCounter is on the edge of max redeliveries? Currently, ActiveMQMessageConsumer _does_ send a poison ack. The problem with that is it creates two messages, as the original stays on the source queue (dlq or otherwise) AND a message to a DLQ (or .DLQ.DLQ when browsing a .DLQ). My argument is that browser should _not_ send a poison ack if the max redelivery count is reached. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information, visit: https://activemq.apache.org/contact
