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/25 13:54:04 UTC

[jira] [Resolved] (AMQ-5863) Composite Send with useCache=false leaves messages pending till restart

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

Gary Tully resolved AMQ-5863.
-----------------------------
    Resolution: Fixed

fix and test in http://git-wip-us.apache.org/repos/asf/activemq/commit/b6fea831

sequence id is cleared *before* store

> Composite Send with useCache=false leaves messages pending till restart
> -----------------------------------------------------------------------
>
>                 Key: AMQ-5863
>                 URL: https://issues.apache.org/jira/browse/AMQ-5863
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: KahaDB, Message Store
>    Affects Versions: 5.11.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.12.0
>
>
> With a composite send, the message id is shared across destinations so the effect of the first store is visible to subsequent stores. This results in the message store considering the second send to be async in error. The relevant state in the message id needs to be reset prior to attempting a send.
> It is sensible to copy the sequence Id state when a message id is copied so that acks can take advantage of the presence of the sequence id without reference to the store.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)