[
https://issues.apache.org/jira/browse/DERBY-4059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674081#action_12674081
]
Kathey Marsden commented on DERBY-4059:
---------------------------------------
I am trying to write a test where having the post commit retries will actually
help, but am having trouble making a case. Even if I change
ClobReclamationTest.xtestMultiThreadedUpdateTableLocking() to have each of the
two threads update just two rows, it seems to give up after three retries. Is
there any wait between retries of post commit actions or does it just loop
through its todo list and retry when it is finished with its current queue?
> If space reclamation cannot obtain container lock it will not retry getting
> the lock
> ------------------------------------------------------------------------------------
>
> Key: DERBY-4059
> URL: https://issues.apache.org/jira/browse/DERBY-4059
> Project: Derby
> Issue Type: Sub-task
> Components: Store
> Affects Versions: 10.1.3.1, 10.2.2.0, 10.3.3.0, 10.4.2.0, 10.5.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
>
> As noted in DERBY-4054 openContainerNW throws an exception if it canno get
> the container lock and bypasses the retry logic. See:
> https://issues.apache.org/jira/browse/DERBY-4054?focusedCommentId=12673376#action_12673376
> We should catch the exception and retry if we can't get the container lock.
> This probably won't fix the repro for DERBY-4054, but should be helpful in
> some user scenarios.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
