db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (DERBY-4967) Handle interrupt received while waiting for database lock
Date Fri, 14 Jan 2011 18:38:46 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12981862#action_12981862
] 

Dag H. Wanvik edited comment on DERBY-4967 at 1/14/11 1:37 PM:
---------------------------------------------------------------

Uploading derby-4967-locking-2, which makes the existing test LockInterruptTest
assert that the interrupt flag is set when we see 08000 (CONN_INTERRUPT).

This was not the case before derby-4967-locking-1 was committed.

Note: On Solaris, the test only asserts the flag this if one of the following conditions hold:

- the flag derbyTesting.safeSolarisInterrupts is true. This can be used for force the assert
to run
  for Solaris with Java 1.6 and lower. The assert will only succeed then if the Java flag
-XX:-UseVMInterruptibleIO is used.
- the test is running on Java 1.7 or higher

If the test is skipped, we do a println to indicate this (iff derby.tests.debug is true).

On other platforms we always do the assert.

BaseTestCase has been extended with two methods to allows tests to determine if they are running
with safe Solaris: #isSolaris and #isSafeSolarisInterrupts

Running regressions.



      was (Author: dagw):
    Uploading derby-4967-locking-2, which makes the existing test LockInterruptTest
assert that the interrupt flag is set when we see 08000 (CONN_INTERRUPT).

This was not the case before derby-4967-locking-1 was committed.

Note: On Solaris, the test only asserts the flag this if one of the following conditions hold:

- the flag derbyTesting.safeSolarisInterrupts is true. This can be used for force the tests
to run
  for Solaris with Java1.6 and lower. The test will then if the Java flag -XX:-UseVMInterruptibleIO
is used.
- the test is running on Java 1.7 or higher

If the test is skipped, we do a println to indicate this (iff derby.tests.debug is true).

On other platforms we always do the assert.

Running regressions.

BaseTestCase has been extended with two methods to allows tests to determine if they are running
with safe Solaris: #isSolaris and #isSafeSolarisInterrupts

  
> Handle interrupt received while waiting for database lock
> ---------------------------------------------------------
>
>                 Key: DERBY-4967
>                 URL: https://issues.apache.org/jira/browse/DERBY-4967
>             Project: Derby
>          Issue Type: Improvement
>          Components: Store
>            Reporter: Dag H. Wanvik
>            Assignee: Dag H. Wanvik
>             Fix For: 10.8.0.0
>
>         Attachments: derby-4967-locking-1.diff, derby-4967-locking-1.stat, derby-4967-locking-2.diff,
derby-4967-locking-2.stat
>
>
> Subtask of DERBY-4741: this issue tracks the changes needed to handle interrupt received
while a thread is waiting for a database lock.

-- 
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