tag:blogger.com,1999:blog-486398466531826618.post550396475024477534..comments2011-02-01T13:25:57.628+02:00Panagiotis Astithashttps://profiles.google.com/116466326438420686438noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-486398466531826618.post-82886695302125277292009-06-16T20:09:51.169+03:002009-06-16T20:09:51.169+03:00Yeah, I checked for OptimisticLockException originally, but for reasons yet to be explained this didn't work reliably for my setup. I'll update the original code if/when I can further limit the transaction rollback causes in a reliable way.pasthttp://www.blogger.com/profile/05077555675379961731noreply@blogger.comtag:blogger.com,1999:blog-486398466531826618.post-19672319163814539802009-06-16T13:26:51.391+03:002009-06-16T13:26:51.391+03:00The EJBTransactionRolledbackException is thrown whenever "the transaction associated with processing of the request has been rolled back, or marked to roll back. Thus the requested operation either could not be performed or was not performed because further computation on behalf of the transaction would be fruitless" as the javadoc says. You might have to check the cause of the EJBTransactionRolledbackException before retrying because it is not certain that it will always be an optimistic lock exception.chstathhttp://www.blogger.com/profile/17356379670827963689noreply@blogger.com