[
https://issues.apache.org/jira/browse/QPID-7684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924640#comment-15924640
]
ASF subversion and git services commented on QPID-7684:
-------------------------------------------------------
Commit 1786939 from [~k-wall] in branch 'java/branches/6.0.x'
[ https://svn.apache.org/r1786939 ]
QPID-7684: [Java Broker, BDB] Adhere to recommended practice for retrying after
a LockConflictException.
Merged from 6.1.x branch with command:
svn merge -c 1786935 ^/qpid/java/branches/6.1.x
> [Java Broker, BDB] Close Cursor when LockConflictException is thrown
> --------------------------------------------------------------------
>
> Key: QPID-7684
> URL: https://issues.apache.org/jira/browse/QPID-7684
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.32, qpid-java-6.0.6, qpid-java-6.1.1,
> qpid-java-broker-7.0.0
> Reporter: Lorenz Quack
> Fix For: qpid-java-6.0.7, qpid-java-6.1.2, qpid-java-broker-7.0.0
>
>
> Currently, when a LockConflictException is thrown we retry the operation.
> However the retry logic does not adhere to the rules outlined in the BDB JE
> documentation, specifically we do not close and recreate the Cursor.
> To quote the
> [documentation|https://docs.oracle.com/cd/E17277_02/html/java/com/sleepycat/je/LockConflictException.html]:
> {quote}If a lock conflict occurs during a transaction, the transaction may be
> retried by performing the following steps. \[...\]:
> # Close all cursors opened under the transaction.
> # Abort the transaction.
> # Begin a new transaction and repeat the operations.
> {quote}
> The impact of not doing this is unclear.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
