[jira] [Created] (AMQ-7071) Messages not marked as redelivered when durable connection closed improperly

["Christopher L. Shannon (JIRA)" <ji...@apache.org>]

Christopher L. Shannon created AMQ-7071:
-------------------------------------------

             Summary: Messages not marked as redelivered when durable connection closed improperly
                 Key: AMQ-7071
                 URL: https://issues.apache.org/jira/browse/AMQ-7071
             Project: ActiveMQ
          Issue Type: Improvement
    Affects Versions: 5.15.6
            Reporter: Christopher L. Shannon
            Assignee: Christopher L. Shannon
             Fix For: 5.16.0


I noticed that if a connection is killed improperly (using kill -9 or network failure, etc) any prefetched messages for a durable subscription are not marked as redelivered because the logic on the broker does not check for the LAST_DELIVERED_UNKNOWN status (-2). 

However, when a queue subscription is closed improperly this flag does get checked.  I think for the durable subscription case we should do the same thing  (match the queue logic) and be checking and marking these messages that were already dispatched but have an unknown status with the JMS redelivery flag as they might potentially be duplicates to the client when the client reconnects.

As a side note this is how Artemis behaves already.



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