Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 85089 invoked from network); 5 May 2010 17:08:25 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 5 May 2010 17:08:25 -0000 Received: (qmail 59654 invoked by uid 500); 5 May 2010 17:08:25 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 59630 invoked by uid 500); 5 May 2010 17:08: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 59623 invoked by uid 99); 5 May 2010 17:08:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 May 2010 17:08:25 +0000 X-ASF-Spam-Status: No, hits=-1392.5 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; Wed, 05 May 2010 17:08:24 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o45H83pB029473 for ; Wed, 5 May 2010 17:08:04 GMT Message-ID: <582933.25141273079283887.JavaMail.jira@thor> Date: Wed, 5 May 2010 13:08:03 -0400 (EDT) From: "Kathey Marsden (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (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:comment-tabpanel&focusedCommentId=12864408#action_12864408 ] Kathey Marsden commented on DERBY-4179: --------------------------------------- Maybe instead it could just loop with 1 second waits for a period of time looking for the database lock file. That way it would wait just as long as needed. It might also help solve the problem of determining if BootLockMinion just didn't do its thing. Sometimes with JVM testing I know the tests are run with various options like turning JIT off which make things run very slowly and so it would be better to have the progress as soon as it is ready but wait 60 seconds total. > 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.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.