[DERBY-5223] Thread's interrupted flag not always preserved after Derby returns from JDBC API call

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.8.1.2
• Fix Version/s: 10.8.2.2, 10.9.1.0
• Component/s: JDBC
• Bug behavior facts: Regression Test Failure
• Assignee: Dag H. Wanvik
• Reporter: Dag H. Wanvik
• Created: 09/May/11 16:25
• Updated: 25/Oct/11 17:09
• Resolved: 27/Jul/11 20:59

Description

Sometimes we have this this stack trace on the log from SuitesAll:

.Exception in thread "WorkerThread. Thread#5" junit.framework.AssertionFailedError
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at junit.framework.Assert.assertTrue(Assert.java:27)
at org.apache.derbyTesting.functionTests.tests.store.InterruptResilienceTest$WorkerThread.run(InterruptResilienceTest.java:430)

This happens sometimes when the application thread's interrupt flag is set before we enter a Derby API call, but the flag is cleared on return contrary to our specified behavior.

Cf mention on https://issues.apache.org/jira/browse/DERBY-5081?focusedCommentId=13030155&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13030155

I can reproduce this every 20 runs or so on Linux with JDK7, but it has been seen also on Windows, so it is not VM specific.

Issue Links

• is part of: DERBY-4741 Make embedded Derby work reliably in the presence of thread interrupts