"triathlon98" wrote : You need to properly configure your load groups. | | Check out the Jboss administration docs for more details about CMP data loading settings and implications. | | Joachim
Thanks for the answer. That is exactly what I have been doing all day. We haven't declared any load groups, yet since we are using JBoss 3.2.6 and the section in standardjbosscmp-jdbc.xml reads | <read-ahead> | <strategy>on-load</strategy> | <page-size>1000</page-size> | <eager-load-group>*</eager-load-group> | </read-ahead> | it has been my understanding that by default JBoss will use an on-load read-ahead strategy with _all_ cmp fields included in its eager-load-group. This seems to contradict the behaviour we are observing. Or am I mistaken? Browsing through some old log files it _seems_ as if this behaviour occured after switching from JBoss 3.2.3 to JBoss 3.2.6. Unfortunately, due to some other problems, we cannot use JBoss 3.2.3 anymore. So does anyone have any info regarding differences in the CMP engine between JBoss 3.2.3 and JBoss 3.2.6 which could help to explain this phenomenon? Thanks, Olaf View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3868689#3868689 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3868689 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
