[
https://issues.apache.org/jira/browse/AMQ-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467600#comment-13467600
]
Lars Hvile commented on AMQ-2870:
---------------------------------
This error still exists when using the JDBC store..
2012-10-02 11:55:57,299 | TRACE | ignoring unmatched selector ack for:
ID:java-dev-image-37369-1349171756956-0:1:1:1:1, cleanup will get to this
message after subsequent acks. |
org.apache.activemq.store.jdbc.JDBCTopicMessageStore | ActiveMQ Transport:
tcp:///127.0.0.1:34884
The cleanup will of course never get to this message, as no messages are acked
ever..
This exclusion of unmatched selectors happens at
https://fisheye6.atlassian.com/browse/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/store/jdbc/JDBCTopicMessageStore.java?r=1345202#to73
It was introduced as a fix to some other bugs in
https://fisheye6.atlassian.com/changelog/activemq?cs=1025939
> Messages that don't match a message selector for a durable subscription are
> stored causing the persistent store to eventually fill up
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-2870
> URL: https://issues.apache.org/jira/browse/AMQ-2870
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.3.2
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.4.1
>
>
> With a durable sub, ack entries are created on a message send for each
> durable sub, but if the durable sub does not match the message due to a
> selector, the message remains unacked, pending, such that is can fill up the
> store. Any unmatched message should be acked immediately.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
