db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From d..@apache.org
Subject svn commit: r887305 - /db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/store/Derby151Test.java
Date Fri, 04 Dec 2009 18:10:07 GMT
Author: dag
Date: Fri Dec  4 18:10:06 2009
New Revision: 887305

URL: http://svn.apache.org/viewvc?rev=887305&view=rev
Log:
DERBY-4461

Committed fix which resets the interrupt flag in the test's
application thread.  Not resetting it caused issues on Windows and
Linux downstream (in teardown).


Modified:
    db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/store/Derby151Test.java

Modified: db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/store/Derby151Test.java
URL: http://svn.apache.org/viewvc/db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/store/Derby151Test.java?rev=887305&r1=887304&r2=887305&view=diff
==============================================================================
--- db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/store/Derby151Test.java
(original)
+++ db/derby/code/trunk/java/testing/org/apache/derbyTesting/functionTests/tests/store/Derby151Test.java
Fri Dec  4 18:10:06 2009
@@ -150,6 +150,12 @@
             println("Not able to test fix for DERBY-151: No interrupt seen");
         } catch (SQLException e) {
             assertSQLState("XSDG9", e);
+            // Clearing the interrupt flag; makes sense for embedded part of
+            // the test. When running c/s, it would be the server thread which
+            // receives the interrupt, and since db is shut down, that should
+            // be ok for later tests. We need to clear the flag here since, for
+            // embedded, the app thread is affected.
+            Thread.currentThread().interrupted();
         }
     }
 }



Mime
View raw message