You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <de...@db.apache.org> on 2006/05/24 16:11:31 UTC
[jira] Updated: (DERBY-1308) Tests jdbcapi/HoldabilityTest.junit,
jdbcapi/UpdateXXXTest.junit,jdbcapi/SURTest.junit fail on
wctme5.7_foundation
[ http://issues.apache.org/jira/browse/DERBY-1308?page=all ]
Myrna van Lunteren updated DERBY-1308:
--------------------------------------
Attachment: DERBY-1308_20060524.stat
DERBY-1308_20060524.diff
I'm attaching a patch - DERBY-1308_20060524.* - for this issue.
I'd like to get some feedback on the approach I have taken.
The problem is that the j9 jvms do not contain some of the classes available in a full-fledged jvm.
For j9_foundation, there is no java.sql.Driver. For the other versions, there is no support for javax.sql.DataSource, XADataSource, nor ConnectionPooledDataSource.
What was happening is that after the contribution of adding a number of methods returning these various datasources in util/BaseJDBCTestCase.java these j9-jvms would fall over with a ClassDefNotFoundError. Apparently this happened as soon as a method was added that returned one of these not-available classes, even though the tests in question did not actually use those methods.
So, I have 2 questions:
1. could that be a jvm bug - i.e. when should a ClassDefNotFoundError get thrown? In this case, it gets thrown when the superclass is returning a non-available class...
2. Either way, is it acceptable to split the BaseJDBCTestClass in two in the way I did with this patch?
> Tests jdbcapi/HoldabilityTest.junit, jdbcapi/UpdateXXXTest.junit,jdbcapi/SURTest.junit fail on wctme5.7_foundation
> ------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1308
> URL: http://issues.apache.org/jira/browse/DERBY-1308
> Project: Derby
> Type: Bug
> Components: Test, Regression Test Failure
> Versions: 10.2.0.0
> Environment: derby jars used - 10.2.0.0 alpha - (400220), machine is a win2000.
> Reporter: Sunitha Kambhampati
> Assignee: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.2.0.0
> Attachments: DERBY-1308_20060524.diff, DERBY-1308_20060524.stat
>
> 05/05/2006 regression test run of derbyall shows the following test failure with wctme5.7_foundation,
> derbyall/derbyall.fail:jdbcapi/HoldabilityTest.junit
> derbyall/derbyall.fail:jdbcapi/UpdateXXXTest.junit
> derbyall/derbyall.fail:jdbcapi/SURTest.junit
> Diff is a CNFE with ConnectionPoolDataSource.
> ********* Diff file derbyall/jdbcapi/HoldabilityTest.diff
> *** Start: HoldabilityTest jdkJ2ME Foundation Specification v1.0 derbyall:jdbcapi 2006-05-07 11:31:05 ***
> 0 add
> > Exception in thread "main" java.lang.NoClassDefFoundError: javax.sql.ConnectionPoolDataSource
> Test Failed.
> *** End: HoldabilityTest jdkJ2ME Foundation Specification v1.0 derbyall:jdbcapi 2006-05-07 11:31:06 ***
> My guess is these tests need to excluded from running in this environment. Can someone please confirm. Thanks.
--
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