[
https://issues.apache.org/jira/browse/AMQ-8131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17276285#comment-17276285
]
ASF subversion and git services commented on AMQ-8131:
------------------------------------------------------
Commit 2f40261362bb830899f7f369a731b446f795a627 in activemq's branch
refs/heads/master from gtully
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=2f40261 ]
AMQ-8131 - revert treating unmatched as real acks b/c individual acks are not
tracked. make use of enableMessageExpirationOnActiveDurableSubs to ensure
unmatched can eventually expire
> 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)
