I use optimistic locking on JBoss 4. If there are optimistic locking conflicting because data has already changed by another task I get an "org.jboss.tm.JBossRollbackException: Unable to commit" Exception.
Is there any way to exactly determine wether a JBossRollbackException is caused by a optimistic locking conflict and not by any other? Why is there no OptimisticLockException like DeadlockException? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3857523#3857523 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3857523 ------------------------------------------------------- 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://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
