Return-Path: Delivered-To: apmail-ibatis-user-java-archive@www.apache.org Received: (qmail 91312 invoked from network); 13 Oct 2009 02:29:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 13 Oct 2009 02:29:07 -0000 Received: (qmail 76339 invoked by uid 500); 13 Oct 2009 02:29:06 -0000 Delivered-To: apmail-ibatis-user-java-archive@ibatis.apache.org Received: (qmail 76302 invoked by uid 500); 13 Oct 2009 02:29:06 -0000 Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user-java@ibatis.apache.org Delivered-To: mailing list user-java@ibatis.apache.org Received: (qmail 76294 invoked by uid 99); 13 Oct 2009 02:29:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Oct 2009 02:29:06 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of clinton.begin@gmail.com designates 209.85.221.172 as permitted sender) Received: from [209.85.221.172] (HELO mail-qy0-f172.google.com) (209.85.221.172) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Oct 2009 02:29:02 +0000 Received: by qyk2 with SMTP id 2so8452132qyk.21 for ; Mon, 12 Oct 2009 19:28:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=NYxftLu96UAB/mEtUOqT+7tNXQ6MV9qlhMozQ25xTjA=; b=ByccJwI3PMgjRf2ivqwIrWEloIbvPFFhFVCfb5xPaOEsLweUZ9Guu+F5knpPKfOnJ4 ICPfWWolfSTVQVKGBjv56rNJENgKoiVQ6otDJtYhiGsCyX+5w6WPXZnUjUoXcCEPmYXi jdi+cJ7xyByfMmWN3Kr/9bsJD6UuU9GVdq20I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=B19P+68zWgv5CMMdDk3ZfcK2YtwE7dXNJ7r5mF3p2fQ3Ojx8qr2KDK8TaBTzv1241m 77sHWSnxd7GgFVcm7nWlJ93uBUAWnqjNZHKooFKGTaRXXACxN0g96D3YyQXYrzsvrnGj NqtDZlq5VmTklvgEqctPZiYPF+vxKoLCS9otU= MIME-Version: 1.0 Received: by 10.224.46.79 with SMTP id i15mr5356331qaf.58.1255400921471; Mon, 12 Oct 2009 19:28:41 -0700 (PDT) In-Reply-To: <16178eb10909151534r15d75e00ma3b8cc838bc8ea84@mail.gmail.com> References: <25442025.post@talk.nabble.com> <16178eb10909141624y1da3a6b9u83cf818e8f194fdc@mail.gmail.com> <25455710.post@talk.nabble.com> <16178eb10909150853u7e739169u8465bbea0e426d7b@mail.gmail.com> <25457565.post@talk.nabble.com> <16178eb10909151004p5a4b0251p304603782f714f89@mail.gmail.com> <25458817.post@talk.nabble.com> <16178eb10909151534r15d75e00ma3b8cc838bc8ea84@mail.gmail.com> Date: Mon, 12 Oct 2009 20:28:41 -0600 Message-ID: <16178eb10910121928x1c9ea8d2nd9f602e2fb6991bc@mail.gmail.com> Subject: Re: ResultHandler - OutOfMemory Exception From: Clinton Begin To: user-java@ibatis.apache.org Content-Type: multipart/alternative; boundary=001517510b68f99ca40475c7cda6 --001517510b68f99ca40475c7cda6 Content-Type: text/plain; charset=ISO-8859-1 Okay, even though you didn't have a Jira ticket open for this, as an added bonus of rewriting the entire result handler, there's now an optimized implementation that should be able to handle any number of rows, as long as you're not using nested result mapping (which makes it impossible to avoid). Clinton On Tue, Sep 15, 2009 at 4:34 PM, Clinton Begin wrote: > Hmmm... I don't think so. I suppose it would make sense to add that ! :-) > Jira ticket! > > > On Tue, Sep 15, 2009 at 11:57 AM, K. Arnold wrote: > >> >> Out of curiosity, is it possible to create my own DefaultSetResultHandler? >> I >> wrote an plugin that would intercept the call, and I was going to walk >> through the result set myself. Unfortunately I'm not sure how to get the >> parameters that are used in the constructor. Looking at the code it seems >> to jump through some hoops passing the objects through. Is there a >> context >> that contains the references to those that I could use? >> >> >> >> Clinton Begin wrote: >> > >> > Ah, then yes, iBATIS 3 might be more aggressive about using the nested >> > objects cache...(even without join mapping), I can't remember if iBATIS >> 2 >> > would behave the same way. Might be worth a try... if it works in 2, >> then >> > I'll revisit the design to see if I can get 3 to only cache if it >> detects >> > a >> > nested result map. >> > Clinton >> > >> > On Tue, Sep 15, 2009 at 10:44 AM, K. Arnold >> wrote: >> > >> >> >> >> I have not used iBATIS 2 to do a comparison. It is very well that the >> >> assumption given to me about how RowHandler works is false. I am in >> the >> >> process of trying to figure out a good limit size to pick utilizing an >> >> AS400 >> >> jdbc driver working on a DB2 database. >> >> >> >> We have decided that utilizing the select statement with the limit is >> the >> >> better decision choice for us. Now we need to figure out how to >> optimize >> >> it. >> >> >> >> Any suggestions would be appreciated :ninja: >> >> >> >> Just to make sure I understand your reply for any future work. I don't >> >> believe I am using a join mapper. I have a POJO that maps directly to >> a >> >> custom (yet extremely complicated) sql statement. The POJO doesn't >> have >> >> any >> >> collections, and is basically stand alone. It is my understanding from >> >> your >> >> code, that my type of POJO isn't going to utilize the join mapper >> method, >> >> since the next POJO will be unique. >> >> >> >> Clinton Begin wrote: >> >> > >> >> > The difference between RowHandler and ResultHandler is only in name. >> >> They >> >> > did the same thing. >> >> > I'd be interested to know if iBATIS 2.x works for you in this regard. >> >> As >> >> > far >> >> > as I can recall, 2.x had the same design if you invoked the join >> >> mapper... >> >> > >> >> > See, as soon as you try to use a JOIN to load a complex object graph, >> >> we >> >> > need to cache the results so that iBATIS knows to append to the >> parent, >> >> > rather than instantiate a new object. >> >> > >> >> > Clinton >> >> > >> >> > On Tue, Sep 15, 2009 at 9:04 AM, K. Arnold >> >> wrote: >> >> > >> >> >> >> >> >> Thank you for the reply. Is it possible to make the join mapping >> >> cache >> >> a >> >> >> configurable attribute on the mapping file? This is my first time >> >> using >> >> >> Ibatis and I was confidently informed that we could walk row by row >> >> over >> >> >> a >> >> >> result set. I was told to look up the RowHandler interface. It is >> my >> >> >> understanding that in Ibatis 3 that the ResultHandler has replaced >> the >> >> >> RowHandler. Was there a specific design decision made not to allow >> a >> >> row >> >> >> by >> >> >> row walk through? >> >> >> >> >> >> As a work around I was looking into the Plugin feature. It looks >> like >> >> I >> >> >> can >> >> >> Intercept the resultSetsHandler method, and write my own code to >> >> process >> >> >> it. >> >> >> In theory I could utilize the DefaultResultSetHandler code and >> remove >> >> the >> >> >> cache feature in my implementation. However I am not sure if I have >> >> >> access >> >> >> to the same constructor parameters at the point of the intercept. >> >> >> >> >> >> There is some concern around the performance of also introducing >> >> multiple >> >> >> call backs to the Database for each "set" of data to process. I >> need >> >> to >> >> >> balance the design choice of writing my own resultSetsHandler with >> the >> >> >> number of sql calls being made to the database via an offset Select >> >> call. >> >> >> >> >> >> I appreciate your replies to this subject. >> >> >> >> >> >> Clinton Begin wrote: >> >> >> > >> >> >> > The nestedResultObjects is necessary for join mapping. One way to >> >> deal >> >> >> > with >> >> >> > this though, is to use batches of reads as well as writes. Use >> the >> >> >> > pagination facilities and possibly even the proprietary >> offset/limit >> >> >> > features of your database to grab subsets of the results. >> >> >> > Incidentally I'm rewriting the DefaultResultSetHandler to be >> easier >> >> to >> >> >> > understand. But I don't see the need for that cache going away >> >> anytime >> >> >> > soon... >> >> >> > >> >> >> > Clinton >> >> >> > >> >> >> > On Mon, Sep 14, 2009 at 1:47 PM, K. Arnold >> >> >> wrote: >> >> >> > >> >> >> >> >> >> >> >> I am trying to iterate over a result set of 2million records, for >> a >> >> >> large >> >> >> >> bulk load and transformation into a new ODS. It appears that I >> am >> >> >> >> getting >> >> >> >> an OutOfMemoryException because the DefaultResultSetHandler is >> >> caching >> >> >> >> the >> >> >> >> object in the nestedResultObjects property. Is there some >> property >> >> I >> >> >> >> should >> >> >> >> set or statement/ method call I should be using that will allow >> me >> >> to >> >> >> >> process one line at a time and not have the nestedResultObjects >> >> store >> >> >> >> each >> >> >> >> object? >> >> >> >> >> >> >> >> My goal: >> >> >> >> * Grab a row >> >> >> >> * Send it to be processed >> >> >> >> * Once processed, move on to the next row. >> >> >> >> Note: Once a row is processed I no longer need a tie back to the >> >> >> object. >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> I have included the custom ResultHandler, the unit test and the >> >> >> >> configuration file. Please let me know if you need other >> >> information. >> >> >> >> >> >> >> >> package com.primetherapeutics.benplanmgr.entity.rxclaim; >> >> >> >> >> >> >> >> import org.apache.ibatis.executor.result.ResultContext; >> >> >> >> import org.apache.ibatis.executor.result.ResultHandler; >> >> >> >> import org.apache.log4j.Logger; >> >> >> >> >> >> >> >> /** >> >> >> >> * @author kjarnold >> >> >> >> * >> >> >> >> */ >> >> >> >> public class GroupEligibilityResultHandler implements >> ResultHandler >> >> { >> >> >> >> Logger logger = >> >> >> >> Logger.getLogger(GroupEligibilityResultHandler.class); >> >> >> >> >> >> >> >> int count = 0; >> >> >> >> >> >> >> >> public void handleResult(ResultContext context) { >> >> >> >> if(context.getResultObject() != null) { >> >> >> >> count++; >> >> >> >> logger.debug(count); >> >> >> >> } >> >> >> >> //context.stop(); >> >> >> >> } >> >> >> >> >> >> >> >> public int getCount() { >> >> >> >> return count; >> >> >> >> } >> >> >> >> >> >> >> >> } >> >> >> >> >> >> >> >> @Test >> >> >> >> public void getGroupElibibilitiesByResultHandler() { >> >> >> >> Map parameterMap = new >> >> HashMap> >> >> >> String>(); >> >> >> >> parameterMap.put("gelThruDate", "1090101"); >> >> >> >> parameterMap.put("addDate", "1090911"); >> >> >> >> parameterMap.put("chgDate", "1090911"); >> >> >> >> parameterMap.put("planDate", "1090101"); >> >> >> >> try { >> >> >> >> GroupEligibilityResultHandler handler = >> new >> >> >> >> GroupEligibilityResultHandler(); >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> session.select("com.primetherapeutics.benplanmgr.entity.rxclaim.data.GroupEligibilityMapper.getGroupEligibilities", >> >> >> >> parameterMap, handler); >> >> >> >> logger.debug(handler.getCount()); >> >> >> >> >> >> >> >> } finally { >> >> >> >> session.close(); >> >> >> >> } >> >> >> >> >> >> >> >> } >> >> >> >> >> >> >> >> >> >> >> >> Here are my mapping files: >> >> >> >> >> >> >> >> >> >> >> >> > >> >> 3.0//EN" >> >> >> >> "http://ibatis.apache.org/dtd/ibatis-3-config.dtd"> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> > >> >> >> >> >> >> >> >> >> >> >> >> >> resource="com/primetherapeutics/benplanmgr/entity/rxclaim/data/BenefitMaxSchedule.xml"/> >> >> >> >> > >> >> >> >> >> >> >> >> >> >> >> >> >> resource="com/primetherapeutics/benplanmgr/entity/rxclaim/data/GroupEligibility.xml"/> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> >> View this message in context: >> >> >> >> >> >> >> >> >> >> http://www.nabble.com/ResultHandler---OutOfMemory-Exception-tp25442025p25442025.html >> >> >> >> Sent from the iBATIS - User - Java mailing list archive at >> >> Nabble.com. >> >> >> >> >> >> >> >> >> >> >> >> >> >> --------------------------------------------------------------------- >> >> >> >> To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org >> >> >> >> For additional commands, e-mail: >> user-java-help@ibatis.apache.org >> >> >> >> >> >> >> >> >> >> >> > >> >> >> > >> >> >> >> >> >> -- >> >> >> View this message in context: >> >> >> >> >> >> http://www.nabble.com/ResultHandler---OutOfMemory-Exception-tp25442025p25455710.html >> >> >> Sent from the iBATIS - User - Java mailing list archive at >> Nabble.com. >> >> >> >> >> >> >> >> >> >> --------------------------------------------------------------------- >> >> >> To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org >> >> >> For additional commands, e-mail: user-java-help@ibatis.apache.org >> >> >> >> >> >> >> >> > >> >> > >> >> >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/ResultHandler---OutOfMemory-Exception-tp25442025p25457565.html >> >> Sent from the iBATIS - User - Java mailing list archive at Nabble.com. >> >> >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org >> >> For additional commands, e-mail: user-java-help@ibatis.apache.org >> >> >> >> >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/ResultHandler---OutOfMemory-Exception-tp25442025p25458817.html >> Sent from the iBATIS - User - Java mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org >> For additional commands, e-mail: user-java-help@ibatis.apache.org >> >> > --001517510b68f99ca40475c7cda6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Okay, even though you didn't have a Jira ticket open for this, as an ad= ded bonus of rewriting the entire result handler, there's now an optimi= zed implementation that should be able to handle any number of rows, as lon= g as you're not using nested result mapping (which makes it impossible = to avoid).=A0

Clinton=A0

On Tue, Sep 15,= 2009 at 4:34 PM, Clinton Begin <clinton.begin@gmail.com> wrote:
Hmmm... I don't think so. I suppose it would make sense to add that ! = =A0:-)

Jira ticket!=A0
=

On Tue, Sep 15, 2009 at 11:57 AM, K. Arn= old <akarnold@comcast.net> wrote:

Out of curiosity, is it possible to create my own DefaultSetResultHandler? = =A0I
wrote an plugin that would intercept the call, and I was going to walk
through the result set myself. =A0Unfortunately I'm not sure how to get= the
parameters that are used in the constructor. =A0Looking at the code it seem= s
to jump through some hoops passing the objects through. =A0Is there a conte= xt
that contains the references to those that I could use?



Clinton Begin wrote:
>
> Ah, then yes, iBATIS 3 might be more aggressive about using the nested=
> objects cache...(even without join mapping), I can't remember if i= BATIS 2
> would behave the same way. =A0Might be worth a try... if it works in 2= , then
> I'll revisit the design to see if I can get 3 to only cache if it = detects
> a
> nested result map.
> Clinton
>
> On Tue, Sep 15, 2009 at 10:44 AM, K. Arnold <akarnold@comcast.net> wrote:
>
>>
>> I have not used iBATIS 2 to do a comparison. =A0It is very well th= at the
>> assumption given to me about how RowHandler works is false. =A0I a= m in the
>> process of trying to figure out a good limit size to pick utilizin= g an
>> AS400
>> jdbc driver working on a DB2 database.
>>
>> We have decided that utilizing the select statement with the limit= is the
>> better decision choice for us. =A0Now we need to figure out how to= optimize
>> it.
>>
>> Any suggestions would be appreciated :ninja:
>>
>> Just to make sure I understand your reply for any future work. =A0= I don't
>> believe I am using a join mapper. =A0I have a POJO that maps direc= tly to a
>> custom (yet extremely complicated) sql statement. =A0The POJO does= n't have
>> any
>> collections, and is basically stand alone. =A0It is my understandi= ng from
>> your
>> code, that my type of POJO isn't going to utilize the join map= per method,
>> since the next POJO will be unique.
>>
>> Clinton Begin wrote:
>> >
>> > The difference between RowHandler and ResultHandler is only i= n name.
>> =A0They
>> > did the same thing.
>> > I'd be interested to know if iBATIS 2.x works for you in = this regard.
>> As
>> > far
>> > as I can recall, 2.x had the same design if you invoked the j= oin
>> mapper...
>> >
>> > See, as soon as you try to use a JOIN to load a complex objec= t graph,
>> we
>> > need to cache the results so that iBATIS knows to append to t= he parent,
>> > rather than instantiate a new object.
>> >
>> > Clinton
>> >
>> > On Tue, Sep 15, 2009 at 9:04 AM, K. Arnold <akarnold@comcast.net> >> wrote:
>> >
>> >>
>> >> Thank you for the reply. =A0Is it possible to make the jo= in mapping
>> cache
>> a
>> >> configurable attribute on the mapping file? =A0 This is m= y first time
>> using
>> >> Ibatis and I was confidently informed that we could walk = row by row
>> over
>> >> a
>> >> result set. =A0I was told to look up the RowHandler inter= face. =A0It is my
>> >> understanding that in Ibatis 3 that the ResultHandler has= replaced the
>> >> RowHandler. =A0Was there a specific design decision made = not to allow a
>> row
>> >> by
>> >> row walk through?
>> >>
>> >> As a work around I was looking into the Plugin feature. = =A0It looks like
>> I
>> >> can
>> >> Intercept the resultSetsHandler method, and write my own = code to
>> process
>> >> it.
>> >> In theory I could utilize the DefaultResultSetHandler cod= e and remove
>> the
>> >> cache feature in my implementation. =A0However I am not s= ure if I have
>> >> access
>> >> to the same constructor parameters at the point of the in= tercept.
>> >>
>> >> There is some concern around the performance of also intr= oducing
>> multiple
>> >> call backs to the Database for each "set" of da= ta to process. =A0I need
>> to
>> >> balance the design choice of writing my own resultSetsHan= dler with the
>> >> number of sql calls being made to the database via an off= set Select
>> call.
>> >>
>> >> I appreciate your replies to this subject.
>> >>
>> >> Clinton Begin wrote:
>> >> >
>> >> > The nestedResultObjects is necessary for join mappin= g. =A0One way to
>> deal
>> >> > with
>> >> > this though, is to use batches of reads as well as w= rites. =A0Use the
>> >> > pagination facilities and possibly even the propriet= ary offset/limit
>> >> > features of your database to grab subsets of the res= ults.
>> >> > Incidentally I'm rewriting the DefaultResultSetH= andler to be easier
>> to
>> >> > understand. =A0But I don't see the need for that= cache going away
>> anytime
>> >> > soon...
>> >> >
>> >> > Clinton
>> >> >
>> >> > On Mon, Sep 14, 2009 at 1:47 PM, K. Arnold <akarnold@comcast.net>
>> >> wrote:
>> >> >
>> >> >>
>> >> >> I am trying to iterate over a result set of 2mil= lion records, for a
>> >> large
>> >> >> bulk load and transformation into a new ODS. =A0= It appears that I am
>> >> >> getting
>> >> >> an OutOfMemoryException because the DefaultResul= tSetHandler is
>> caching
>> >> >> the
>> >> >> object in the nestedResultObjects property. =A0I= s there some property
>> I
>> >> >> should
>> >> >> set or statement/ method call I should be using = that will allow me
>> to
>> >> >> process one line at a time and not have the nest= edResultObjects
>> store
>> >> >> each
>> >> >> object?
>> >> >>
>> >> >> My goal:
>> >> >> * Grab a row
>> >> >> * Send it to be processed
>> >> >> * Once processed, move on to the next row.
>> >> >> Note: Once a row is processed I no longer need a= tie back to the
>> >> object.
>> >> >>
>> >> >>
>> >> >>
>> >> >> I have included the custom ResultHandler, the un= it test and the
>> >> >> configuration file. =A0Please let me know if you= need other
>> information.
>> >> >>
>> >> >> package com.primetherapeutics.benplanmgr.entity.= rxclaim;
>> >> >>
>> >> >> import org.apache.ibatis.executor.result.ResultC= ontext;
>> >> >> import org.apache.ibatis.executor.result.ResultH= andler;
>> >> >> import org.apache.log4j.Logger;
>> >> >>
>> >> >> /**
>> >> >> =A0* @author kjarnold
>> >> >> =A0*
>> >> >> =A0*/
>> >> >> public class GroupEligibilityResultHandler imple= ments ResultHandler
>> {
>> >> >> =A0 =A0 =A0 =A0Logger logger =3D
>> >> >> Logger.getLogger(GroupEligibilityResultHandler.c= lass);
>> >> >>
>> >> >> =A0 =A0 =A0 =A0int count =3D 0;
>> >> >>
>> >> >> =A0 =A0 =A0 =A0public void handleResult(ResultCo= ntext context) {
>> >> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0if(context.getRes= ultObject() !=3D null) {
>> >> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0c= ount++;
>> >> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0l= ogger.debug(count);
>> >> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0}
>> >> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0//context.stop();=
>> >> >> =A0 =A0 =A0 =A0}
>> >> >>
>> >> >> =A0 =A0 =A0 =A0public int getCount() {
>> >> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0return count;
>> >> >> =A0 =A0 =A0 =A0}
>> >> >>
>> >> >> }
>> >> >>
>> >> >> =A0 =A0 =A0 =A0@Test
>> >> >> =A0 =A0 =A0 =A0public void getGroupElibibilities= ByResultHandler() {
>> >> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Map<String, St= ring> parameterMap =3D new
>> HashMap<String,
>> >> >> String>();
>> >> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0parameterMap.put(= "gelThruDate", "1090101");
>> >> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0parameterMap.put(= "addDate", "1090911");
>> >> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0parameterMap.put(= "chgDate", "1090911");
>> >> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0parameterMap.put(= "planDate", "1090101");
>> >> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0try {
>> >> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0G= roupEligibilityResultHandler handler =3D new
>> >> >> GroupEligibilityResultHandler();
>> >> >>
>> >> >>
>> >> >>
>> >>
>> session.select("com.primetherapeutics.benplanmgr.entity.rxcla= im.data.GroupEligibilityMapper.getGroupEligibilities",
>> >> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0parameterMap, handler);
>> >> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0l= ogger.debug(handler.getCount());
>> >> >>
>> >> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0} finally {
>> >> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0s= ession.close();
>> >> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0}
>> >> >>
>> >> >> =A0 =A0 =A0 =A0}
>> >> >>
>> >> >>
>> >> >> Here are my mapping files:
>> >> >>
>> >> >> <?xml version=3D"1.0" encoding=3D&q= uot;UTF-8" ?>
>> >> >> <!DOCTYPE configuration PUBLIC "-//ibatis.apache.org//D= TD Config
>> >> 3.0//EN"
>> >> >> =A0 =A0 =A0 =A0"http://ibatis.apache.or= g/dtd/ibatis-3-config.dtd">
>> >> >> <configuration>
>> >> >> <settings>
>> >> >> =A0 =A0 =A0 =A0<setting name=3D"multiple= ResultSetsEnabled" value=3D"false"/>
>> >> >> =A0 =A0 =A0 =A0<setting name=3D"defaultE= xecutorType" value=3D"BATCH"/>
>> >> >> </settings>
>> >> >> =A0 =A0 =A0 =A0<mappers>
>> >> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<mapper
>> >> >>
>> >> >>
>> >>
>> resource=3D"com/primetherapeutics/benplanmgr/entity/rxclaim/d= ata/BenefitMaxSchedule.xml"/>
>> >> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<mapper
>> >> >>
>> >> >>
>> >>
>> resource=3D"com/primetherapeutics/benplanmgr/entity/rxclaim/d= ata/GroupEligibility.xml"/>
>> >> >> =A0 =A0 =A0 =A0</mappers>
>> >> >> </configuration>
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> View this message in context:
>> >> >>
>> >>
>> http://www.nabble.com/Resu= ltHandler---OutOfMemory-Exception-tp25442025p25442025.html
>> >> >> Sent from the iBATIS - User - Java mailing list = archive at
>> Nabble.com.
>> >> >>
>> >> >>
>> >> >>
>> ------------------------------------------------------------------= ---
>> >> >> To unsubscribe, e-mail: user-java-unsubscribe@= ibatis.apache.org
>> >> >> For additional commands, e-mail: user-java-help@ibati= s.apache.org
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/Resu= ltHandler---OutOfMemory-Exception-tp25442025p25455710.html
>> >> Sent from the iBATIS - User - Java mailing list archive a= t Nabble.com.
>> >>
>> >>
>> >> ---------------------------------------------------------= ------------
>> >> To unsubscribe, e-mail: user-java-unsubscribe@ibatis.ap= ache.org
>> >> For additional commands, e-mail: user-java-help@ibatis.apache.= org
>> >>
>> >>
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Resu= ltHandler---OutOfMemory-Exception-tp25442025p25457565.html
>> Sent from the iBATIS - User - Java mailing list archive at Nabble.= com.
>>
>>
>> ------------------------------------------------------------------= ---
>> To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org<= /a>
>> For additional commands, e-mail: user-java-help@ibatis.apache.org >>
>>
>
>

--
View this message in context: http:= //www.nabble.com/ResultHandler---OutOfMemory-Exception-tp25442025p25458817.= html
Sent from the iBATIS - User - Java mailing list= archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
For additional commands, e-mail: user-java-help@ibatis.apache.org



--001517510b68f99ca40475c7cda6--