Hi, our application is running with JBoss 3.2.5 on two linux servers. We do not use clustering, but Commit Option C with row-locking for much of our entity beans:
| <container-configuration extends="Instance Per Transaction CMP 2.x EntityBean"> | <container-name>Standard CMP 2.x EntityBean with Commit Option C</container-name> | <commit-option>C</commit-option> | </container-configuration> | The database could (sometimes) be changed by other application. Without | Instance Per Transaction CMP 2.x EntityBean | we get Deadlock on big load. Why? Now I'm thinking about change the container configuration to commit option B. Will it be better for my application? Best Regards, Rafal View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872019#3872019 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872019 ------------------------------------------------------- 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 JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
