We had an application that used the default "standard bmp entity bean configuration" with pessimistic locking. The application used to hang and get into deadlocks frequently. The hang went away as soon as we shifted it to use "Instance Per Transaction BMP EntityBean" with NoLock. We are concerned though that this might result in concurrent update problems. My question here is: Is it legal to change the "Instance Per Transaction BMP EntityBean" configuration in standardjboss.xml to use optimistic locking to prevent possible concurrency problems? By default the standardjboss.xml uses NoLock for this configuration.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876467#3876467 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876467 ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
