The rollback exception you see is caused by | Caused by: org.jboss.cache.CacheException: unable to validate nodes | at org.jboss.cache.interceptors.OptimisticValidatorInterceptor.validateNodes(OptimisticValidatorInt | erceptor.java:109) |
which is the result of 2 or more threads attempting to concurrently modify some data. Since data is optimistically locked (i.e., copied and versioned) there is always the potential for an exception like this to be thrown. Still though, with the new OptimisticTreeCacheProvider using the Option API (http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheOptionsAPI) - specifically the failSilent option - this exception should not bubble up anywhere but simply be logged. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3933987#3933987 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3933987 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
