Instability in storerecovery suite when run against jar files on jdk1.6
-----------------------------------------------------------------------

         Key: DERBY-1460
         URL: http://issues.apache.org/jira/browse/DERBY-1460
     Project: Derby
        Type: Bug

  Components: Store  
    Versions: 10.2.0.0    
 Environment: linux, build 88 of mustang jdk1.6
    Reporter: Rick Hillegas


I am seeing the following errors in oc_rec3 when I run the storerecovery suite 
against jar files on linux under jdk1.6 (Mustang build 88). This is a 
Heisenbug: I ran the suite 20 times and saw the problem in 10 of those runs. 
For the record, I don't see this problem on cygwin/xp using Mustang build 88 
(on that platform, I also ran the suite 20 times but saw no errors).

Here are the oc_rec3 diffs:

*** Start: oc_rec3 jdk1.6.0-rc storerecovery:storerecovery 2006-06-27 12:00:42 
***
1 del
< Beginning test: test1
2 del
< Ending test: test1
2 add
> Exception in thread "main" SQL Exception: Failed to start database 'wombat', 
> see the next exception for details.
> Caused by: SQL Exception: Failed to start database 'wombat', see the next 
> exception for details.
>       ... 20 more
Test Failed.
*** End:   oc_rec3 jdk1.6.0-rc storerecovery:storerecovery 2006-06-27 12:00:45 
***

Here are the contents of oc_rec3.tmp:

Exception in thread "main" java.sql.SQLException: Failed to start database 
'wombat', see the next exception for details.
        at 
org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
        at 
org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown
 Source)
        at 
org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source)
        at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown 
Source)
        at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(Unknown 
Source)
        at org.apache.derby.impl.jdbc.EmbedConnection.bootDatabase(Unknown 
Source)
        at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown Source)
        at org.apache.derby.impl.jdbc.EmbedConnection30.<init>(Unknown Source)
        at org.apache.derby.impl.jdbc.EmbedConnection40.<init>(Unknown Source)
        at org.apache.derby.jdbc.Driver40.getNewEmbedConnection(Unknown Source)
        at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)
        at java.sql.DriverManager.getConnection(DriverManager.java:548)
        at java.sql.DriverManager.getConnection(DriverManager.java:148)
        at org.apache.derby.impl.tools.ij.util.startJBMS(Unknown Source)
        at org.apache.derby.impl.tools.ij.util.startJBMS(Unknown Source)
        at org.apache.derby.impl.tools.ij.util.startJBMS(Unknown Source)
        at org.apache.derby.tools.ij.startJBMS(Unknown Source)
        at 
org.apache.derbyTesting.functionTests.tests.store.oc_rec3.main(Unknown Source)
Caused by: SQL Exception: Failed to start database 'wombat', see the next 
exception for details.
        ... 20 more




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to