I think that starting with JBoss 3.2.3 the CMP engine has undergone more or 
less drastic changes in order to accommodate more and more performance tuning 
switches. I have the _impression_ that  as a side-effect JBoss does not honor 
some settings in standardjbosscmp-jdbc.xml anymore.

We managed to restitute the old behaviour by adding something like

  | @jboss.read-ahead
  |            strategy = "on-load"
  |            page-size = "1000"
  |            eager-load-group = "*"
  |  
  | @jboss.lazy-load-group
  |            name = "*"
  | 
to our EBs. Don't ask me about the exact meaning of these tags. Any time I read 
the CMP chapter in the JBoss docs I _think_ I finally got my head around it, 
only to see myself crashing into the next inexplicable phenomenon a few days 
later.

Cheers,

Olaf

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873200#3873200

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873200


-------------------------------------------------------
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

Reply via email to