[ http://issues.apache.org/jira/browse/DERBY-1499?page=all ]
Myrna van Lunteren updated DERBY-1499:
--------------------------------------
Attachment: DERBY-1499_102_20060712.diff
I rethought my earlier solution, so the newer patch - DERBY-1499_20060712.diff
- changes RunList.java to check on the util.TestUtil field HAVE_DRIVER_CLASS.
This way the solution is not dependent on any jvm version.
> test run exits for _foundation run because unloadEmbeddedDriver uses
> driverManager, which isn't available.
> ----------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1499
> URL: http://issues.apache.org/jira/browse/DERBY-1499
> Project: Derby
> Type: Bug
> Components: Test
> Versions: 10.2.0.0
> Environment: windows - with wctme5.7_foundation
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Attachments: DERBY-1499_102_20060711.diff, DERBY-1499_102_20060712.diff
>
> The wctme5.7_foundation runs have been exiting out for a while.
> We only run this environment weekly and were under the impression there was a
> time out. But I ran the suite, capturing the output in a file, and the last
> part of the run shows the problem is with unloadEmbeddedDriver:
> Now do RunList
> Exception in thread "main" java.lang.NoClassDefFoundError:
> java.sql.DriverManager
> at
> org.apache.derbyTesting.functionTests.harness.RunList.unloadEmbeddedDriver(RunList.java:1636)
> at
> org.apache.derbyTesting.functionTests.harness.RunList.runSuites(RunList.java:276)
> at
> org.apache.derbyTesting.functionTests.harness.RunList.<init>(RunList.java:167)
> at
> org.apache.derbyTesting.functionTests.harness.RunSuite.getSuitesList(RunSuite.java:208)
> at
> org.apache.derbyTesting.functionTests.harness.RunSuite.main(RunSuite.java:147)
> UnloadEmbeddedDriver was put in to allow running with useprocess=false and
> autoload of the driver, so it's needed.
> But maybe we can add an appropriate if condition so it doesn't try to do this
> with foundation.
--
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
