From derby-dev-return-77913-apmail-db-derby-dev-archive=db.apache.org@db.apache.org Tue May 04 22:06:25 2010 Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 43170 invoked from network); 4 May 2010 22:06:25 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 4 May 2010 22:06:25 -0000 Received: (qmail 54314 invoked by uid 500); 4 May 2010 22:06:25 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 54256 invoked by uid 500); 4 May 2010 22:06:25 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 54249 invoked by uid 99); 4 May 2010 22:06:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 May 2010 22:06:25 +0000 X-ASF-Spam-Status: No, hits=-1387.9 required=10.0 tests=ALL_TRUSTED,AWL X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 May 2010 22:06:24 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o44M63Pa017274 for ; Tue, 4 May 2010 22:06:03 GMT Message-ID: <30083094.4061273010763428.JavaMail.jira@thor> Date: Tue, 4 May 2010 18:06:03 -0400 (EDT) From: "Dag H. Wanvik (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (DERBY-4179) bootLock.java fails with missing exception on z/OS with pmz3160sr2ifix-20081021_01(SR2+IZ32776+IZ33456), and Windows Vista In-Reply-To: <189435336.1240416587451.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-4179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dag H. Wanvik updated DERBY-4179: --------------------------------- Attachment: derby-4179-junit.diff derby-4179-junit.stat Uploading a patch which rewrites store/bootLock to JUnit. If the test fails, the subprocess will leave its log file around for inspection. It appears to run happily with relative jars. I notice that the old test properties had these settings: -runwithj9=false -runwithibm13=false -runwithjdk13=false The latter is stale and probably ibm13 as well(?), but please let me know if the "j9" exception is still relevant, and if so, how my test should skip the test for this platform. > 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.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.