Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 26837 invoked from network); 1 Apr 2008 07:38:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Apr 2008 07:38:41 -0000 Received: (qmail 13992 invoked by uid 500); 1 Apr 2008 07:38:40 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 13642 invoked by uid 500); 1 Apr 2008 07:38:39 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 13631 invoked by uid 99); 1 Apr 2008 07:38:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Apr 2008 00:38:39 -0700 X-ASF-Spam-Status: No, hits=-1.0 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [192.18.6.21] (HELO gmp-eb-inf-1.sun.com) (192.18.6.21) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Apr 2008 07:37:47 +0000 Received: from fe-emea-09.sun.com (gmp-eb-lb-2-fe1.eu.sun.com [192.18.6.10]) by gmp-eb-inf-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m317c3kR027471 for ; Tue, 1 Apr 2008 07:38:07 GMT Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JYM00001XGN8O00@fe-emea-09.sun.com> (original mail from Dyre.Tjeldvoll@Sun.COM) for derby-user@db.apache.org; Tue, 01 Apr 2008 08:38:03 +0100 (BST) Received: from khepri32.sun.com ([129.159.112.244]) by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JYM002J4YIJ6K20@fe-emea-09.sun.com> for derby-user@db.apache.org; Tue, 01 Apr 2008 08:37:31 +0100 (BST) Date: Tue, 01 Apr 2008 09:37:30 +0200 From: Dyre.Tjeldvoll@Sun.COM Subject: Re: ERROR XSDG2: Invalid checksum on Page Page(0,Container(0, 1313)) In-reply-to: <47F163C3.3010502@nuix.com> Sender: Dyre.Tjeldvoll@Sun.COM To: Derby Discussion Message-id: MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT References: <47F02F3E.40807@nuix.com> <47F065D0.6010404@sun.com> <47F074A0.40309@nuix.com> <47F163C3.3010502@nuix.com> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (usg-unix-v) X-Virus-Checked: Checked by ClamAV on apache.org David Sitsky writes: > For what its worth, I did another run last night on my 6 quad-core > system. This time I had the derby issue happen for a JVM process on > machine 1, two processes on machine 4, and one on machine 5. I run > four JVM processes per quad-core machine. > > All the JVM processes have roughly the same data processing rate, but > the issue happens at different times into the load. The problem > occurred around time 420, 480, 800 and 900 minutes into the load for > the four problematic processes. Just to clarify: These jvm processes do not access the SAME database, do they? -- dt