We have an issue with Entity beans that are being configured as read-only getting locked into transactions. We configured these entity beans as read only in the jboss.xml file, used "RequiresNew" transaction attribute for all methods in these beans and used commit option 'A' for these beans.
But entity lock monitor in jmx-console still shows locking time and contention for some of these beans. We have no clue why those beans are still getting locked into container transactions. Any of you have this kind of issue? Can you please explain what I am missing here? Your help is greatly appreciated. Thank you very much in advance. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3878948#3878948 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3878948 ------------------------------------------------------- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
