I am using commit option A on entity beans, so that there is no redundant ejbLoad of entity beans between transactions. But this means for 2 concurrent transactions, even if they were read-only operations, one would be locked out till the other completed, since the global instance cache is pessimistically locked.
How do I devise a strategy to let read-only transactions proceed simultaneously (not one after other) despite using commit option A ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863210#3863210 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3863210 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
