[
http://issues.apache.org/jira/browse/DERBY-1746?page=comments#action_12431037 ]
Myrna van Lunteren commented on DERBY-1746:
-------------------------------------------
For the record, this is the 'full' stack trace from the .tmp file (no derby.log
appears to get created)
START - phase CREATE
java.lang.ExceptionInInitializerError
at org.apache.derby.jdbc.EmbeddedDataSource.findDriver(Unknown Source)
at org.apache.derby.jdbc.EmbeddedDataSource.getConnection(Unknown
Source)
at org.apache.derby.jdbc.EmbeddedDataSource.getConnection(Unknown
Source)
at
org.apache.derbyTesting.functionTests.tests.upgradeTests.UpgradeTester.getConnectionUsingDataSource(UpgradeTester.java:461)
at
org.apache.derbyTesting.functionTests.tests.upgradeTests.UpgradeTester.getConnection(UpgradeTester.java:418)
at
org.apache.derbyTesting.functionTests.tests.upgradeTests.UpgradeTester.runPhase(UpgradeTester.java:357)
at
org.apache.derbyTesting.functionTests.tests.upgradeTests.UpgradeTester.runUpgradeTests(UpgradeTester.java:317)
at
org.apache.derbyTesting.functionTests.tests.upgradeTests.Upgrade_10_1_10_2.main(Upgrade_10_1_10_2.java:44)
Caused by: java.lang.SecurityException: sealing violation: can't seal package
org.apache.derby.iapi.services.crypto: already loaded
at java.net.URLClassLoader.defineClass(URLClassLoader.java:234)
at java.net.URLClassLoader.access$100(URLClassLoader.java:55)
at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:141)
at
org.apache.derby.impl.services.monitor.BaseMonitor.getImplementations(Unknown
Source)
at
org.apache.derby.impl.services.monitor.BaseMonitor.getDefaultImplementations(Unknown
Source)
at
org.apache.derby.impl.services.monitor.BaseMonitor.runWithState(Unknown Source)
at org.apache.derby.impl.services.monitor.FileMonitor.<init>(Unknown
Source)
at org.apache.derby.iapi.services.monitor.Monitor.startMonitor(Unknown
Source)
at org.apache.derby.iapi.jdbc.JDBCBoot.boot(Unknown Source)
at org.apache.derby.jdbc.EmbeddedDriver.boot(Unknown Source)
at org.apache.derby.jdbc.EmbeddedDriver.<clinit>(Unknown Source)
... 8 more
Exception in thread "main"
> upgrade tests should start using 10.1.3 released builds
> -------------------------------------------------------
>
> Key: DERBY-1746
> URL: http://issues.apache.org/jira/browse/DERBY-1746
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.2.1.0
> Reporter: Myrna van Lunteren
> Assigned To: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.2.1.0
>
> Attachments: DERBY-1746_102_20060823.diff,
> DERBY-1746_102_20060823.stat, DERBY-1746_trunk_20060824.diff
>
>
> The upgrade test' master is based on the 10.1 jars checked in to svn -
> 10.1.1.0 - (208786).
> However, we now have a newer released version of 10.1 - 10.1.3. This would
> be the obvious choice for someone running tests testing the beta jars.
> If the jars are 10.1.3 then a diff will occur because of the fix for
> DERBY-655:
> 703d702
> <
> ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx,
> 7
> 2168d2166
> <
> ,APP,DERBY655T2,C21_ID,,APP,DERBY655T1,C11_ID,1,3,0,F_12,xxxxGENERATED-IDxxxx,
> 7
> It would be nice if the final build for 10.2 would include an updgrade test
> master created using 10.1.3, And same is true for the trunk.
--
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
