The new persistence manager is in 3.2.5. But I would recommend at least 3.2.6 as there were valuable improvements in caching.
The container does cache instances in case of Standard container configuration. Plus there is read-ahead cache which a per-transaction cache. Each invocation might change the persistence context either in business method or container internally by loading/initializing the instance. You can set threshold to DEBUG for org.jboss.ejb.plugins.cmp category in log4j and see what SQL container executes. ejbLoad is not called if instance is cached. In other words, if instance is in the cache it is in the ready state. I guess your instances are evicted from the cache due to reached maximum cache capacity or age out. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3859187#3859187 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3859187 ------------------------------------------------------- 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://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
