Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 40388 invoked from network); 27 Apr 2009 23:49:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 27 Apr 2009 23:49:53 -0000 Received: (qmail 81925 invoked by uid 500); 27 Apr 2009 23:49:53 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 81882 invoked by uid 500); 27 Apr 2009 23:49:53 -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 81869 invoked by uid 99); 27 Apr 2009 23:49:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Apr 2009 23:49:53 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Apr 2009 23:49:51 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 5DAFD234C003 for ; Mon, 27 Apr 2009 16:49:30 -0700 (PDT) Message-ID: <1593645187.1240876170369.JavaMail.jira@brutus> Date: Mon, 27 Apr 2009 16:49:30 -0700 (PDT) From: "Mike Matrigali (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (DERBY-4181) SQLState.LANG_IGNORE_MISSING_INDEX_ROW_DURING_DELETE during NsTest run In-Reply-To: <236156022.1240438487720.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-4181: ---------------------------------- In my environment (xp, 2 processor laptop, trunk) I reproduced a couple of times within 5 minutes on ibm16. I tried in same environment 2 times with ibm15 and 2 times with sun16 and let them go at least 15 minutes each as did not see any issues. So now the question is whether this is an ibm16 jvm bug, or is ibm16 just more concurrent and showing up a derby bug. I have definitely seem real derby bugs that are multi-thread timing only show up on ibm16. I think this may be the first time we have run this test against ibm16, as I think ibm15 was the chosen ibm jvm during the 10.3 and 10.4 release cycles. Here is my exact jvm info: ibm16: m2_ibm16:55>java -version java version "1.6.0" Java(TM) SE Runtime Environment (build pwi3260sr3-20081106_07(SR3)) IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260-2008110 _25433 (JIT enabled, AOT enabled) J9VM - 20081105_025433_lHdSMr JIT - r9_20081031_1330 GC - 20081027_AB) JCL - 20081106_01 ibm15: java version "1.5.0" Java(TM) 2 Runtime Environment, Standard Edition (build pwi32dev-20080315 (SR7)) IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223-2008031 5 (JIT enabled) J9VM - 20080314_17962_lHdSMr JIT - 20080130_0718ifx2_r8 GC - 200802_08) JCL - 20080314 sun16: java version "1.6.0_01" Java(TM) SE Runtime Environment (build 1.6.0_01-b06) Java HotSpot(TM) Client VM (build 1.6.0_01-b06, mixed mode) > SQLState.LANG_IGNORE_MISSING_INDEX_ROW_DURING_DELETE during NsTest run > ----------------------------------------------------------------------- > > Key: DERBY-4181 > URL: https://issues.apache.org/jira/browse/DERBY-4181 > Project: Derby > Issue Type: Bug > Components: Store > Affects Versions: 10.4.2.0, 10.5.1.0, 10.5.1.1, 10.6.0.0 > Environment: Suse Linux 10, IBM 1.6 SR4 > Reporter: Myrna van Lunteren > Attachments: run1serverlog.jar, serverlog.jar > > > During the NsTest runs for 10.5.1.0 and 10.5.1.1 I initially ignored warnings showing up in the server's derby.log file: > WARNING: While deleting a row from a table the index row for base table row (594,12) was not found in index with conglomerate id 1,185. This problem has automatically been corrected as part of the delete operation. > However, I don't think this is a completely healthy warning, I think it indicates there was corruption in the index. > I'll investigate further. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.