[AMQ-5277] JDBC ack does not use messageId.entryLocator

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.10.0
• Fix Version/s: 5.10.1, 5.11.0
• Component/s: Broker, Message Store
• Labels: jdbc performance
• Assignee: Gary Tully
• Reporter: Gary Tully
• Created: 14/Jul/14 15:57
• Updated: 17/Dec/14 02:51
• Resolved: 14/Jul/14 21:19

Description

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.