[jira] [Created] (AMQ-7090) Message keeps being redelivered to new connections, regardless of policy

["Arjen (JIRA)" <ji...@apache.org>]

Arjen created AMQ-7090:
--------------------------

             Summary: Message keeps being redelivered to new connections, regardless of policy
                 Key: AMQ-7090
                 URL: https://issues.apache.org/jira/browse/AMQ-7090
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
    Affects Versions: 5.15.7
         Environment: Ubuntu 18.04 host with ActiveMQ 5.15.7. Software was php 7.2 with the 3.4 stomp client.
            Reporter: Arjen
         Attachments: activemq.xml

We have a setup with Activemq with php-stomp producers and consumers for queues. One of those consumers crashed prior to acknowledging a message and was automatically restarted. It got the message again, crashed again, etc... Since this was an unmonitored test-environment, it had restarted several million times ;)

The crash isn't really relevant here, but we wanted to prevent this from happening again. The  [redelivery pluging|http://activemq.apache.org/message-redelivery-and-dlq-handling.html] seemed to be a match; configure it to send messages over a certain redelivery count to the DLQ and we'd be done.

Unfortunately, it doesn't seem to work. With the attached configuration we connected a test-consumer that would never acknowledge a message, sent a message and killed the test-consumer. Repeating this beyond the configured maximumRedeliveries had no effect, we kept getting the same message. Via the web-interface, we could see it was clearly keeping track of those redeliveries though.

Somewhat related, the whole redelivery-configuration seems to be irrelevant, the message was available on the queue right away, without any of the 'backoff' and 'delay' visible.

So summarized steps to reproduce:
 * Configure ActiveMQ according to the documentation with redeliveryPlugin
 * Connect to a queue with a consumer (with Stomp?) that will not acknowledge a message, but will display what it got
 * Send a message
 * Disconnect/kill consumer
 * Reconnect the test consumer
 * Repeat previous to see it keeps getting the same message



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)