db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2277) Make it possible to run the testsuite with jdk1.7
Date Wed, 07 Feb 2007 22:50:05 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471137

Myrna van Lunteren commented on DERBY-2277:

I committed the README.htm changes with revision 504724, (with one minor change - 1.7 instead
of 1.6 for the second occurrence). see http://svn.apache.org/viewvc?view=rev&revision=504724.

That text re being able to run with the same jvm class...
Well, it is possible that a new jvm reports itself as one of the existing jvms. 
The harness tries to come up with a likely classname to call with Class.forName, based on
jvm-properties. Over time, the set of variables to check has been added to, presumably because
theoretically similar jvms behaved differently (causing different output and requiring new
master/canon branches and/or different special properties). Currently, it checks for java.vm.name,
java.vm.vendor, java.vm.version, and com.ibm.oti.configuration. So, if your new vm has a different
value for any of those properties, the harness will attempt to instantiate a non-existing
class. And, so you'll need either a new jvm class (boo), or changes to the harness (worse).

> Make it possible to run the testsuite with jdk1.7
> -------------------------------------------------
>                 Key: DERBY-2277
>                 URL: https://issues.apache.org/jira/browse/DERBY-2277
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>         Environment: jdk1.7
>            Reporter: Vemund Østgaard
>         Assigned To: Vemund Østgaard
>            Priority: Trivial
>             Fix For:
>         Attachments: 2277-diff, 2277-diff.stat, 2277-diff2, 2277-diff2, 2277-diff2.stat,
> Today if you try to run the testsuite with jdk1.7 you get a ClassNotFoundException:
> Process exception: java.lang.ClassNotFoundException: org.apache.derbyTesting.functionTests.harness.jdk17
> Exception in thread "main" java.lang.ClassNotFoundException: org.apache.derbyTesting.functionTests.harness.jdk17
>    at java.net.URLClassLoader$1.run(URLClassLoader.java:203)
>    at java.security.AccessController.doPrivileged(Native Method)
>    at java.net.URLClassLoader.findClass(URLClassLoader.java:191)
>    at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
>    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
>    at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
>    at java.lang.Class.forName0(Native Method)
>    at java.lang.Class.forName(Class.java:169)
>    at org.apache.derbyTesting.functionTests.harness.jvm.getJvm(Unknown Source)
>    at org.apache.derbyTesting.functionTests.harness.RunTest.buildTestCommand(Unknown
>    at org.apache.derbyTesting.functionTests.harness.RunTest.testRun(Unknown Source)
>    at org.apache.derbyTesting.functionTests.harness.RunTest.main(Unknown Source) 

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

View raw message