harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Hindess (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-6296) [classlib][sql][test] derby.jar used in java5 testing required java6 classes
Date Thu, 13 Aug 2009 13:46:14 GMT

    [ https://issues.apache.org/jira/browse/HARMONY-6296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742822#action_12742822

Mark Hindess commented on HARMONY-6296:

Nathan: No particular test - just all tests that require the derby driver to be loaded.

Testing with -Dtest.case=org.apache.harmony.sql.tests.internal.rowset.JoinRowSetTest and
adding Java 6 classes one by one, I found that if I *prepend* the following set of Java 6
classes to the bootclasspath then the test executes with no failures nor errors:


The first time it works (after a clean-test) the derby.log file complains about the database
not existing subsequent runs have no errors/warnings in derby.log.

I tried removing the prepended Java 6 classes - after running the tests successfully and creating
the database - but the exception still occurs so it is *not* related to the database not existing
on the first run.

The tests should probably remove the database once the test run has completed.

This makes me pretty sure that we are using a derby.jar that is not suitable for java5 use.

> [classlib][sql][test] derby.jar used in java5 testing required java6 classes
> ----------------------------------------------------------------------------
>                 Key: HARMONY-6296
>                 URL: https://issues.apache.org/jira/browse/HARMONY-6296
>             Project: Harmony
>          Issue Type: Bug
>          Components: Classlib
>            Reporter: Mark Hindess
> I see errors with the sql tests on java5 occasionally.  The test failures just shows
that the driver is unregistered but derby.log contains:
>   ERROR XBM01: Startup failed due to an exception. See next exception for details. 
>   ...
>   Caused by: java.lang.NoClassDefFoundError: java.sql.SQLTransientConnectionException
> Adding missing java6 classes causes the tests to pass reliably.  I wonder if there is
a version of derby.jar more suitable for java 5 testing?

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message