db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-1606) derbyrunjartest hangs with wctme5.7 & always uses j9_13
Date Fri, 28 Jul 2006 11:57:13 GMT
derbyrunjartest hangs with wctme5.7 & always uses j9_13

                 Key: DERBY-1606
                 URL: http://issues.apache.org/jira/browse/DERBY-1606
             Project: Derby
          Issue Type: Test
    Affects Versions:
            Reporter: Myrna van Lunteren
            Priority: Minor
             Fix For:

derbyrunjartest hangs with wctme5.7.

I am not sure what the hook up is but if I do this:
j9 -jcl:max -Xbootclasspath/p:c:/wctme5.7/ive/lib/jclMax/classes.zip;c:/wctme5.7/ive/lib/charconv.zip;c:/wctme5.7/ive/lib/database_enabler.jar
-jar c:/derbyt/svn2/trunk/jars/sane/derbyrun.jar ij --help
I get successfully:
Usage: java org.apache.derby.tools.ij [-p propertyfile] [-ca connectionAttribute
PropertyFile] [inputfile]

Also, when looking at the code of this test, it forces the jvm class to be used to be j9_13
whenever the jvm as set in RunTest starts with J9. However, wctme5.7 is j9_22 and this also
prevents running with foundation (assuming that's supported).

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


View raw message