[ http://issues.apache.org/jira/browse/DERBY-1606?page=all ]
Rick Hillegas updated DERBY-1606: --------------------------------- Fix Version/s: 10.2.3.0 (was: 10.2.2.0) Move to 10.2.3.0. > derbyrunjartest hangs with wctme5.7 & always uses j9_13; hangs with > _foundation > ------------------------------------------------------------------------------- > > Key: DERBY-1606 > URL: http://issues.apache.org/jira/browse/DERBY-1606 > Project: Derby > Issue Type: Test > Components: Test > Affects Versions: 10.0.2.0 > Reporter: Myrna van Lunteren > Priority: Minor > Fix For: 10.2.3.0 > > Attachments: DERBY-1606_20060730_skip.diff, > DERBY-1606_20060731_skipcomment.diff > > > 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