From me@caoilte.org  Wed Jan 29 12:06:08 2003
Return-Path: <me@caoilte.org>
Mailing-List: contact turbine-torque-user-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list turbine-torque-user@jakarta.apache.org
Received: (qmail 2725 invoked from network); 29 Jan 2003 12:06:08 -0000
Received: from gadolinium.btinternet.com (194.73.73.111)
  by daedalus.apache.org with SMTP; 29 Jan 2003 12:06:08 -0000
Received: from host217-44-186-195.range217-44.btcentralplus.com ([217.44.186.195] helo=192.168.1.28)
	by gadolinium.btinternet.com with esmtp (Exim 3.22 #16)
	id 18dqyl-0007Mw-00
	for turbine-torque-user@jakarta.apache.org; Wed, 29 Jan 2003 12:06:07 +0000
From: Caoilte O'Connor <me@caoilte.org>
Reply-To: me@caoilte.org
To: turbine-torque-user@jakarta.apache.org
Subject: doSelectJoin causing stack overflow.
Date: Wed, 29 Jan 2003 12:06:05 +0000
User-Agent: KMail/1.5
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200301291206.05708.me@caoilte.org>
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Hi,
I want to use the nifty doSelectJoin methods in the BasePeers for my webapp, 
but they keep causing a

java.lang.StackOverflowError

They're selecting over some fairly large tables, so I guess that's a possible 
reason, except I've tried setting limits in the criteria and adding quite 
specific criterias and I always get the same error. It doesn't happen for 
smaller tables I have, but nearly always for any function which is 
doSelectJoinAllExcept*

That suggests the Peer is getting too many results to handle, but I can't find 
out for sure as whenever I stick debugging code in the BasePeer java files it 
gets ignored (serialized class files elsewhere getting used instead?).

here's my criteria

crit.add(SportCategoryDetailPeer.LANGUAGE_ID, getLanguageId());
crit.add(SportCategoryPeer.SPORT_CODE_ID, getSportCodeId());
crit.setLimit(20);
List results= SportCategoryDetailPeer.doSelect(crit);

(should generate 10 results - a join on an empty criteria generates 300);

anyone any idea why my app is recursing too deeply? 

i'm running jdk1.4.1 and standalone torque3.0


caoilte