Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 37221 invoked from network); 9 Jun 2006 02:47:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 9 Jun 2006 02:47:03 -0000 Received: (qmail 20141 invoked by uid 500); 9 Jun 2006 02:46:55 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 20037 invoked by uid 500); 9 Jun 2006 02:46:55 -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 19967 invoked by uid 99); 9 Jun 2006 02:46:54 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Jun 2006 19:46:54 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [203.217.22.128] (HELO file1.syd.nuix.com.au) (203.217.22.128) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Jun 2006 19:46:52 -0700 Received: from [192.168.222.102] (demo1.syd.nuix.com.au [192.168.222.102]) by file1.syd.nuix.com.au (Postfix) with ESMTP id 0B784B735C for ; Fri, 9 Jun 2006 12:46:18 +1000 (EST) Message-ID: <4488E259.1050501@nuix.com.au> Date: Fri, 09 Jun 2006 12:52:09 +1000 From: Daniel Noll Organization: NUIX Pty Limited User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Derby Users Mailing List Subject: Strange assert failure, should I be worried? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi all. Our application was reading from a BLOB stream, and allegedly something went wrong during the transaction (which is why we're seeing rollback here.) We retry in such an event but apparently three failures in a row must have occurred, in which case we give up. What baffles me the most is that I can't see any error with what's actually being displayed on-screen -- the data is all correct. > org.apache.derby.iapi.services.sanity.AssertFailure: ASSERT FAILED setCurrentContextManager - mismatch threads - current Thread[(thread class)$1,6,main] - cm's Thread[(thread class)$1,6,main] > at org.apache.derby.iapi.services.sanity.SanityManager.THROWASSERT(SanityManager.java:150) > at org.apache.derby.iapi.services.context.ContextService.setCurrentContextManager(ContextService.java:333) > at org.apache.derby.impl.jdbc.TransactionResourceImpl.setupContextStack(TransactionResourceImpl.java:274) > at org.apache.derby.impl.jdbc.EmbedConnection.setupContextStack(EmbedConnection.java:1464) > at org.apache.derby.impl.jdbc.EmbedConnection.rollback(EmbedConnection.java:894) > at com.nuix.store.database.DatabaseWrapper.wrap(DatabaseWrapper.java:91) > at com.nuix.store.binary.DatabaseBinaryStore$StoredInputStream.read(DatabaseBinaryStore.java:413) So should I be worried about this kind of error? It's the first time I've ever seen one, and viewing the same data over and over doesn't seem to reproduce the problem. Daniel -- Daniel Noll Nuix Pty Ltd Suite 79, 89 Jones St, Ultimo NSW 2007, Australia Ph: +61 2 9280 0699 Web: http://www.nuix.com.au/ Fax: +61 2 9212 6902 This message is intended only for the named recipient. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this message or attachment is strictly prohibited.