db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4059) If space reclamation cannot obtain container lock it will not retry getting the lock
Date Tue, 17 Feb 2009 19:22:59 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kathey Marsden updated DERBY-4059:
----------------------------------

    Attachment: derby-4059_code_change_diff.txt

Attached is a patch for the code change so that we will retry if we can't get a container
lock.  I cannot however come up with a test case where it seems to make any difference.  As
I commented earlier, the retry seems to be too quick. I manually verified that we do retry
and give up by setting derby.debug.true=DaemonTrace  and looking at the derby.log.

I'd like to come up with a test case though where the retry helps before I check in.


> 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
>         Attachments: derby-4059_code_change_diff.txt
>
>
> 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.


Mime
View raw message