You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2011/08/23 00:50:29 UTC
[jira] [Updated] (DERBY-4647) BaseTestCase.execJavaCmd() does not
work with weme 6.2
[ https://issues.apache.org/jira/browse/DERBY-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-4647:
----------------------------------
Attachment: derby-4667_diff.txt
Attached is a patch for this issue. I am running tests now.
I would appreciate if someone familiar with PhoneME could look at it.
For BootLockTest, J9 (weme 6.2) does not require derby.database.forceDatabaseLock to be set, so now this is only needed for PhoneME() but we don't currently have an isPhoneMEPlatform() method so I am just using
if (JDBC.vmSupportsJSR169() && !isJ9Platform()). What is the best way to identify PhoneME()?
> BaseTestCase.execJavaCmd() does not work with weme 6.2
> ------------------------------------------------------
>
> Key: DERBY-4647
> URL: https://issues.apache.org/jira/browse/DERBY-4647
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.1.0
> Environment: IBM J9 2.4 Windows XP x86-32 (JIT enabled, AOT enabled)
> J9VM - 20080919_023055_lHdFGQ
> JIT - r9.weme62_20080724_2131
> GC - 20080609_AA
> JCL - 20080918_2026,foun11
> Licensed Materials - Property of IBM
> J9 - VM for the Java(TM) platform, Version 2.4
> (c) Copyright IBM Corp. 1991, 2008 All Rights Reserved
> Target: 20080919_023055_lHdFGQ (Windows XP 5.1 build 2600 Service Pack 3 x86)
> IBM is a registered trademark of IBM Corp.
> Java and all Java-based marks and logos are trademarks or registered
> trademarks of Sun Microsystems, Inc.
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Labels: derby_triage10_8
> Attachments: derby-4667_diff.txt
>
>
> Spawning a java process with BaseTestCase.execJavaCmd() does not work with weme 6.2, I think because the boot classpath does not get passed. This issue came up in DERBY-4179. After this issue is fixed, BootLockTest should be enabled for weme.
> 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
> Otherwise, currently I think the method is only used in replication and network server, but am not sure.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira