Unsubscribed durable sub can leave dangling message reference in kahaDB,
visible after a restart
------------------------------------------------------------------------------------------------
Key: AMQ-3206
URL: https://issues.apache.org/jira/browse/AMQ-3206
Project: ActiveMQ
Issue Type: Bug
Components: Message Store
Affects Versions: 5.4.2
Reporter: Gary Tully
Assignee: Gary Tully
Fix For: 5.5.0
Unsubscribing a durable sub with kahaDB cleans up the expected ack locations
but does not update the change to the persistent index. After a restart, the
old state is recovered which can lead to invalid references to messages. These
references can block journal file deletion when the message is ultimately
consumed by all interested subs, Leading to data file build up. The necessary
conditions are multiple durable subs with some unsubscribing with a remaining
backlog along with broker restarts.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
