[QPID-7701] [BDB HA] Cursor#getNext API misuse

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Invalid
• Affects Version/s: qpid-java-6.0, qpid-java-6.1, qpid-java-broker-7.0.0
• Fix Version/s: qpid-java-6.1.2, qpid-java-6.0.7, qpid-java-broker-7.0.0
• Component/s: Broker-J
• Assignee: Keith Wall
• Reporter: Keith Wall
• Created: 13/Mar/17 16:57
• Updated: 02/Oct/19 19:22
• Resolved: 21/Mar/17 10:29

Description

The documentation for methods com.sleepycat.je.Cursor#getNext and com.sleepycat.je.Cursor#getSearchKeyRange notes the following:

In a replicated environment, an explicit transaction must have been
specified when opening the cursor, unless read-uncommitted isolation is
specified via the CursorConfig or LockMode
parameter.

Currently methods such as org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore.BDBMessageStoreReader#visitDistributedTransactions do not do this.

The documentation does not state the implications of not following this advice.