>>From the log/server.log we see that each findByStatus generates a HUGE JH> select statement with around 300 ORs ( SELECT id FROM VPKRITERIE JH> WHERE (id=?) OR (id=?) OR (id=?) OR (id=?) OR (id=?) OR (id=?) OR JH> (id=?) ............
Is that the problem? This is controlled by page-size element in read-ahead. JH> <read-ahead> JH> <strategy>on-find</strategy> JH> <eager-load-group>*</eager-load-group> JH> </read-ahead> JH> We have tried to play around with conf/standardjbosscmp-jdbc.xml and JH> standardjaws.xml, but to no help. The parameteres set is: JH> in standardjbosscmp-jdbc.xml: JH> <read-ahead> JH> <strategy>on-find</strategy> <page-size><OR_numbers_here></page-size> JH> <eager-load-group>*</eager-load-group> JH> </read-ahead> alex ------------------------------------------------------- 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