Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 51866 invoked from network); 16 Sep 2009 18:31:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 16 Sep 2009 18:31:09 -0000 Received: (qmail 35438 invoked by uid 500); 16 Sep 2009 18:31:08 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 35371 invoked by uid 500); 16 Sep 2009 18:31:08 -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 35363 invoked by uid 99); 16 Sep 2009 18:31:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Sep 2009 18:31:08 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [63.82.107.6] (HELO red.amberpoint.com) (63.82.107.6) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Sep 2009 18:30:59 +0000 Received: from [127.0.0.1] (bpendleton-desk.edgility.com [10.10.12.184]) by red.amberpoint.com (8.13.8/8.13.8) with ESMTP id n8GIUaxZ026926 for ; Wed, 16 Sep 2009 11:30:36 -0700 Message-ID: <4AB12ECC.9020309@amberpoint.com> Date: Wed, 16 Sep 2009 11:30:36 -0700 From: Bryan Pendleton User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Derby Discussion Subject: Re: StackOverflowError for large Scrollable result sets References: <4AB0F077.2010608@gmail.com> In-Reply-To: <4AB0F077.2010608@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org > Caused by: org.apache.derby.client.am.SqlException: DERBY SQL error: > SQLCODE: -1, SQLSTATE: XJ001, SQLERRMC: > java.lang.StackOverflowErrorXJ001.U > at org.apache.derby.client.am.ResultSet.completeSqlca(Unknown Source) Is there a more detailed exception trace in your derby.log file? I'd expect to see a stack trace with hundreds, perhaps thousands, of stack frames in it, which is what I usually see in the cases where I've had stack overflow errors. Usually such a stack trace makes it pretty easy to see where there is code that is re-entering itself (possibly indirectly), and causing the stack overflow. If you can't find a more detailed exception trace in the derby.log file, here's another thing you can try to do to get more information: http://wiki.apache.org/db-derby/UnwindExceptionChain thanks, bryan