Hello Jon,
> > > > > > >for (id=0;id++;id<1000) {
> > > > > > > // Start transaction
> > > > > > > Collection c=findByStatus(id,status);
> > > > > > > for(i=c.iterator();i.hasNext();) {
> > > > > > > ((EntityLocal) (i.next())) . setStatus(newStatus);
> > > > > > > }
> > > > > > > // End transaction
> > > > > > >}
>
> From the log/server.log we see that each findByStatus generates a HUGE
> select statement with around 300 ORs ( SELECT id FROM VPKRITERIE
> WHERE (id=?) OR (id=?) OR (id=?) OR (id=?) OR (id=?) OR (id=?) OR
> (id=?) ............
OK, but when you do the "Collection c=findByStatus....", the collection c
that you receives contains at least 300 items, right? Temporarly, let's not
speak about the generated statement in itself, but let's focus on what you
are asking to JBoss.
Can you first confirm that the size of the SQL statement is related to the
size of your collection (or smaller). I mean, can you confirm that the
result of findByStatus is not a collection of 2 items and that the SQL
statement includes 300 ORs.
> We have tried to play around with conf/standardjbosscmp-jdbc.xml and
> standardjaws.xml, but to no help. The parameteres set is:
the best way will be to play, finder by finder, in the jbosscmp-jdbc.xml of
your application once we've understood what is really happening. Playing
with standardjaws.xml is useless unless your using JAWS instead of JBossCMP
(depends on the DocType declaration of ejb-jar.xml)
Cheers,
Sacha
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
