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

Dag H. Wanvik edited comment on DERBY-5081 at 5/10/11 10:09 PM:
----------------------------------------------------------------

[edit: I filed DERBY-5223 for this - it is a different issue] 

Thanks Knut. You are right, the test did not fail (JUnit assert in thread 
doesn't work as one could assume). I'll change that. Since a similar "loss of 
interrupt flag" has also happened on Windows, this is probably not the same 
error as this issue. I'll investigate it.


      was (Author: dagw):
    Thanks Knut. You are right, the test did not fail (JUnit assert in thread 
doesn't work as one could assume). I'll change that. Since a similar "loss of 
interrupt flag" has also happened on Windows, this is probably not the same 
error as this issue. I'll investigate it.

  
> Intermittent failure in InterruptResilienceTest: IO thread times out waiting 
> for another thread to recover channel
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5081
>                 URL: https://issues.apache.org/jira/browse/DERBY-5081
>             Project: Derby
>          Issue Type: Bug
>          Components: Store, Test
>    Affects Versions: 10.8.1.2
>         Environment: Linux/JDK 7
> Java 7 (b135) on Debian 5.0
> OEL/JDK7
>            Reporter: Knut Anders Hatlen
>         Attachments: derby-5081-compensate.diff, derby.log, derby.log
>
>
> A couple of failures have been seen in InterruptResilienceTest lately: (Edit: 
> Dag. this issue is for the first one only, the second issue has been 
> allocated DERBY-5140)
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.7/testing/testlog/lin/1075421-suitesAll_diff.txt
>  :
> testRAFWriteInterrupted(org.apache.derbyTesting.functionTests.tests.store.InterruptResilienceTest)java.sql.SQLException:
>  DERBY SQL error: SQLCODE: -1, SQLSTATE: 38000, SQLERRMC: 
> java.sql.SQLException: Derby thread received an interrupt during a disk I/O 
> operation, please check your application for the source of the 
> interrupt.38000XSDG9:XSDG9.D
>   at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown 
> Source)
>   at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
>   at org.apache.derby.client.am.Statement.executeUpdate(Unknown Source)
>   at 
> org.apache.derbyTesting.functionTests.tests.store.InterruptResilienceTest.testRAFWriteInterrupted(InterruptResilienceTest.java:204)
> [edit: treatment of this is moved to DERBY-5140: Windows 2003/Java 1.4.2 - 
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.4/testing/testlog/w2003/1075087-suitesAll_diff.txt:
>   
>   
> testRAFReadWriteMultipleThreads(org.apache.derbyTesting.functionTests.tests.store.InterruptResilienceTest)java.sql.SQLException:
>  The exception 'java.lang.InterruptedException' was thrown while evaluating 
> an expression.
>     at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown 
> Source)
>     at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
>     at org.apache.derby.impl.jdbc.Util.seeNextException(Unknown Source)
>     at 
> org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown 
> Source)
>     at 
> org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown 
> Source)
>     at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown 
> Source)
>     at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown 
> Source)
>     at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown 
> Source)
>     at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source)
>     at org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(Unknown Source)
>     at 
> org.apache.derbyTesting.functionTests.tests.store.InterruptResilienceTest.testRAFReadWriteMultipleThreads(InterruptResilienceTest.java:515)
> ]

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to