Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Mon, 14 Jul 2014 21:20:08 +0000 (UTC)
From: "Gary Tully (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12727110.1405353461228.39167.1405372808441@arcas>
In-Reply-To: <JIRA.12727110.1405353461228@arcas>
References: <JIRA.12727110.1405353461228@arcas>
Subject: [jira] [Resolved] (AMQ-5277) JDBC ack does not use
 messageId.entryLocator
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Gary Tully resolved AMQ-5277.
-----------------------------

    Resolution: Fixed

fix in http://git-wip-us.apache.org/repos/asf/activemq/commit/3b5d89a7

> JDBC ack does not use messageId.entryLocator
> --------------------------------------------
>
>                 Key: AMQ-5277
>                 URL: https://issues.apache.org/jira/browse/AMQ-5277
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, Message Store
>    Affects Versions: 5.10.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>              Labels: jdbc, performance
>             Fix For: 5.11.0
>
>
> The jdbc message store was doing a jdbc roundtrip to find the sequence id of a message before a remove. this information was being retained in the messageId entryLocator on insert.
> However it was not being recreated on a recover and it was lost on a message ack unless vm transport was in play.
> By reusing the entryLocator information there is a ~30% improvement in simple produce/consume roundrtip tests. 


--
This message was sent by Atlassian JIRA
(v6.2#6252)