[jira] [Updated] (AMQ-5277) JDBC ack does not use messageId.entryLocator

["Hadrian Zbarcea (JIRA)" <ji...@apache.org>]

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

Hadrian Zbarcea updated AMQ-5277:
---------------------------------
    Fix Version/s: 5.10.1

> 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.10.1, 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.3.4#6332)