[
https://issues.apache.org/jira/browse/DERBY-4179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864562#action_12864562
]
Kathey Marsden commented on DERBY-4179:
---------------------------------------
Well I guess we aren't as set up to spawn a j9 process as I thought.
The error is actually
.JVMJ9VM011W Unable to load jclfoun10_24: The specified module could not be foun
d.
JVMEXEX013E Internal VM error: Failed to create Java VM
JVMEXEX014I Run C:\cygwin\ibmsvn\ntsoftware\weme6.2\bin\j9.exe -help for usage
execJavaProcess does pick up the j9 executable but does not pass on the other
settings.
This is how my script invokes the test with j9. It probably has a lot of
legacy system properties not needed, but I suppose execJavaCmd should just pass
along all system properties, but I don't know how it would get the
bootclasspath. Perhaps -Dbootcp was a way to pass it on in the old harness.
c:/cygwin/ibmsvn/ntsoftware/weme6.2/bin/j9 -jcl:foun11 -DderbyTesting.serverho
st=localhost -DderbyTesting.clienthost=localhost -Demma.active= -Xbootclasspath/
a:c:/cygwin/ibmsvn/ntsoftware/weme6.2/lib/jdbc.jar -Dbootcp=c:/cygwin/ibmsvn/nts
oftware/weme6.2/lib/jdbc.jar junit.textui.TestRunner org.apache.derbyTesting.fun
ctionTests.tests.store.BootLockTest
Anyway I best get back to my 10.6 testing. Disabling for J2ME for now and and
adding an issue to enable it later would be fine by me. It might be convenient
to have the code below to print the error output on error.
....
catch (SocketTimeoutException e) {
p.destroy();
p.waitFor();
// Print error output
BufferedReader er = new BufferedReader(new
InputStreamReader(p.getErrorStream()));
String failmsg = "Minion did not start or boot db in 60 seconds\n";
String erout= null ;
do {
erout = er.readLine();
if (erout != null) failmsg += erout;
} while (erout != null);
fail(failmsg);
}
> bootLock.java fails with missing exception on z/OS with
> pmz3160sr2ifix-20081021_01(SR2+IZ32776+IZ33456), and Windows Vista
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-4179
> URL: https://issues.apache.org/jira/browse/DERBY-4179
> Project: Derby
> Issue Type: Bug
> Components: Store, Test
> Affects Versions: 10.5.1.1
> Environment: java version "1.6.0"
> Java(TM) SE Runtime Environment (build
> pmz3160sr2ifix-20081021_01(SR2+IZ32776+IZ33456))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 z/OS s390-31
> jvmmz3160ifx-20081010_24288 (JIT enabled, AOT enabled)
> J9VM - 20081009_024288_bHdSMr
> JIT - r9_20080721_1330ifx2
> GC - 20080724_AA)
> JCL - 20080808_02
> ------------------------------------------
> Also seen on : Vista Ultimate 32 bits under cygwin with Sun JRE 1.6.0_07-b06
> Reporter: Kathey Marsden
> Assignee: Dag H. Wanvik
> Attachments: bootLock.diff, derby-4179-junit-2.diff,
> derby-4179-junit-2.stat, derby-4179-junit-3.diff, derby-4179-junit-3.stat,
> derby-4179-junit.diff, derby-4179-junit.stat, derby-4179.diff,
> derby-4179.stat, derbyall_report.txt, storeall_report.txt, sysinfo.txt
>
>
> I saw this diff in store/bootLock.java. I did not see it with the 64bit jvm
> run on 10.5.1.0 RC1
> *** Start: bootLock jdk1.6.0 storeall:storemore 2009-04-21 19:10:18 ***
> 2,4d1
> < expected exception
> < SQLSTATE(XJ040):
> < SQLSTATE(XSDB6):
> Test Failed.
> *** End: bootLock jdk1.6.0 storeall:storemore 2009-04-21 19:11:00 ***
> The test passed on rerun when run independently.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
