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 2015/06/26 12:52:04 UTC
[jira] [Resolved] (AMQ-5864) KahaDB recovery with
persisteRedeliveryFlag=true can lead to stuck message
[ https://issues.apache.org/jira/browse/AMQ-5864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully resolved AMQ-5864.
-----------------------------
Resolution: Fixed
fix and test in http://git-wip-us.apache.org/repos/asf/activemq/commit/2c53dbcc
> KahaDB recovery with persisteRedeliveryFlag=true can lead to stuck message
> --------------------------------------------------------------------------
>
> Key: AMQ-5864
> URL: https://issues.apache.org/jira/browse/AMQ-5864
> Project: ActiveMQ
> Issue Type: Bug
> Components: KahaDB
> Affects Versions: 5.11.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Fix For: 5.12.0
>
>
> I send a message to queue "in" and then kill -9 the broker. After the restart, sometimes the message is lost and I can see following in broker log:
> Duplicate message add attempt rejected. Destination: QUEUE://in, Message id: ID:abe-ThinkPad-T430s-55936-1434452370587-1:1:1:1:1
> Without the {code}<policyEntry ... persistJMSRedelivery=true/>{code} I'm unable to reproduce this issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)