You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Gary Tully (Jira)" <ji...@apache.org> on 2021/02/01 09:53:00 UTC

[jira] [Reopened] (AMQ-8131) JDBC Store - durable topic with non matching selector can hold message till unsubscribe in error

     [ https://issues.apache.org/jira/browse/AMQ-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully reopened AMQ-8131:
-----------------------------

need to rethink, I see a failure in org.apache.activemq.usecases.DurableSubscriptionOffline3Test#testOfflineSubscriptionWithSelectorAfterRestart when there is a gap in unacked, pointing to the need to track each ack individually.
It may be that it is best to treat the durable sub that never gets a message as the special case.

> JDBC Store - durable topic with non matching selector can hold message till unsubscribe in error
> ------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-8131
>                 URL: https://issues.apache.org/jira/browse/AMQ-8131
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JDBC, Message Store
>    Affects Versions: 5.16.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>            Priority: Major
>             Fix For: 5.17.0
>
>
> Unmatched messages get an unmatched ack, however this ack is ignored by the topic message store under the assumption that there will be some subsequent ack that will more the cursor forward and allow cleanup to happen. However this may never happen and messages can accumulate till that subscription is removed.
> The jdbc topic message store needs to track the unmatched acks in the normal way.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)