[ http://issues.apache.org/jira/browse/DERBY-1606?page=all ]
Myrna van Lunteren updated DERBY-1606:
--------------------------------------
Summary: derbyrunjartest hangs with wctme5.7 & always uses j9_13; hangs
with _foundation (was: derbyrunjartest hangs with wctme5.7 & always uses j9_13)
And now that I've got a foundation run going, I found this test hangs with that
jvm.
I think it is because the test does not pass on required properties, and again,
it's trying to run j9_13, which is not correct wctme5.7_foundation, we need
j9_foundation.
For info, this is the process that I think is hanging:
myrna 6100 4564 0 06:28:43 xyz 0:00 j9 -Duser.language=en
-Duser.country=US -Xbootclasspath/a:null -jar
C:/p4/p4main/opensource/jars/insane/derbyrun.jar ij --help
Note the -Xbootclasspath/a:null.
The output shows it did try to get going; derbyrunjartest.tmp shows:
ij --help:
I suggest we stop this test from running with these jvms until the problem can
be addressed.
> 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
> Affects Versions: 10.0.2.0
> Reporter: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.2.0.0
>
>
> 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
