Solved it! Apparently it had nothing to do with read-only beans but with the way JBoss 4.0.2 checks for dirty entity beans. Upgrading to 4.0.3SP1 solved the problem.
BTW, the performance increase is HUGE. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3916038#3916038 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3916038 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
