Hi, Thanks for your comments. Your issue with pess. locking is unrelated. It's to do with Hibernate using putFailFast() on JBoss Cache, which should suppress and ignore such failures. Hibernate does not care if cache put()'s fail, and hence overrides the timeout with 0. The error message should be suppressed in this case since this is not an error but expected behaviour in this use case.
I'm still looking into this issue with opt. locking. Basically from what I gather, it is only a matter of time before you start seeing this? Do you have a lot of concurrent writes to the data? Cheers, Manik View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3946283#3946283 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3946283 ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
