[
https://issues.apache.org/jira/browse/QPID-7701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy resolved QPID-7701.
------------------------------
Resolution: Fixed
> [BDB HA] Cursor#getNext API misuse
> ----------------------------------
>
> Key: QPID-7701
> URL: https://issues.apache.org/jira/browse/QPID-7701
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: qpid-java-6.0, qpid-java-6.1, qpid-java-broker-7.0.0
> Reporter: Keith Wall
> Assignee: Keith Wall
> Fix For: qpid-java-6.0.7, qpid-java-6.1.2, qpid-java-broker-7.0.0
>
>
> The documentation for methods {{com.sleepycat.je.Cursor#getNext}} and
> {{com.sleepycat.je.Cursor#getSearchKeyRange}} notes the following:
> {quote}
> 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.
> {quote}
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
