Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 60445 invoked from network); 8 Feb 2008 13:15:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Feb 2008 13:15:16 -0000 Received: (qmail 70580 invoked by uid 500); 8 Feb 2008 13:15:08 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 70551 invoked by uid 500); 8 Feb 2008 13:15: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 70540 invoked by uid 99); 8 Feb 2008 13:15:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Feb 2008 05:15:08 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of acidbriggs@gmail.com designates 209.85.198.189 as permitted sender) Received: from [209.85.198.189] (HELO rv-out-0910.google.com) (209.85.198.189) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Feb 2008 13:14:38 +0000 Received: by rv-out-0910.google.com with SMTP id b22so2508053rvf.55 for ; Fri, 08 Feb 2008 05:14:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=Q9WZ1GI62sXQwQYUdTIceV5Sq8uM7uO+rvg1CEYxkFU=; b=lCvUN19iy7t2zKEdo6HtiAjm5aceME6LvyExQkGHxZeDlQHyBHUgjlDcs2/SSc6ieJWW0Q4BQsMNbfl5cqZBPs0NGO3s5wzQ92MPoPeazlIvMLxpKuYGD+znvFzQ5ASIhuFmYNEwBCdElFkVpvO7pOMFN1Sap/1QzFJLjE5Lc6o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=c5e6RqL4mw3391oCLh2NaLitqL7wduq0wm8JDkQTAqezPo+eq0MI6LNiwKyIl4QAZCDNU6Qp7h7pqA3rwJHnyUAwlkDcmI2iWrHJ//g332yM+1l+GxAJ4kLnOygNWWlH9Ue+yXpHzsuiofPoXrwNNx2ZStbiDFXAd8GJfDgPwkk= Received: by 10.141.34.12 with SMTP id m12mr8500372rvj.26.1202476485984; Fri, 08 Feb 2008 05:14:45 -0800 (PST) Received: by 10.141.116.14 with HTTP; Fri, 8 Feb 2008 05:14:45 -0800 (PST) Message-ID: <1c0e93080802080514i50df5cb0sea0e65f59ca39dd5@mail.gmail.com> Date: Fri, 8 Feb 2008 08:14:45 -0500 From: Briggs To: "Derby Discussion" Subject: Iterating through large result set in network mode causes OutOfMemoryException MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org So, I have a derby database that could potentially contain millions of records, but at the moment it has 13K. I am trying to iterate through that table after calling a basic "Select * from myTable". After about 5000 records, I get an out of memory exception/error on the server side. This table has very a couple small clobs in it (each field contains about only 100 chars at the moment) and one large clob. I have no transactions running, the result set is read only. I would think that I should be able to loop through an infinite set of results. If I do this in embedded mode it's fine. I have read over 10 million records with no problem. But, again, in network mode it fails early. Anyone have any advice? I would think that a non-scrollable result set should not keep any of the results in memory (on the server) once the cursor has passed it. -- "Conscious decisions by conscious minds are what make reality real"