Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 18246 invoked from network); 6 May 2007 15:49:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 May 2007 15:49:36 -0000 Received: (qmail 87455 invoked by uid 500); 6 May 2007 15:49:42 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 87424 invoked by uid 500); 6 May 2007 15:49:42 -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 87415 invoked by uid 99); 6 May 2007 15:49:42 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 06 May 2007 08:49:42 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 06 May 2007 08:49:35 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 4FEF1714064 for ; Sun, 6 May 2007 08:49:15 -0700 (PDT) Message-ID: <3204506.1178466555294.JavaMail.jira@brutus> Date: Sun, 6 May 2007 08:49:15 -0700 (PDT) From: "Knut Anders Hatlen (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-2141) BlobClob4BlobTest.testPositionBlob() fails with NullPointerException In-Reply-To: <12345655.1165229481076.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493936 ] Knut Anders Hatlen commented on DERBY-2141: ------------------------------------------- > before adding the synchonization, what effect will that have on possible finalizer/synchronization deadlock? Depends on what we synchronize on. If we synchronize on the connection sync object, it could definitely lead to deadlocks since we sometimes call System.runFinalization() while holding the monitor on the object. Having a synchronized flag or something locally in BaseContainerHandle that only prevented threads to enter close() concurrently would be safe, I think. > BlobClob4BlobTest.testPositionBlob() fails with NullPointerException > -------------------------------------------------------------------- > > Key: DERBY-2141 > URL: https://issues.apache.org/jira/browse/DERBY-2141 > Project: Derby > Issue Type: Bug > Components: Regression Test Failure > Affects Versions: 10.3.0.0 > Environment: Java SE 6, Java SE 5.0 (less frequently). Linux and Solaris. > Reporter: Knut Anders Hatlen > Attachments: stacktrace.diff > > > Seen in the nightly regression tests: > http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/testlog/lin/481811-org.apache.derbyTesting.functionTests.suites.All_diff.txt > http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/testlog/lin/480626-org.apache.derbyTesting.functionTests.suites.All_diff.txt -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.