I assume you have multiple JobExecutors going. Then the StaleObject exceptions are to be expected when multiple threads try to lock the jobs. One jobexecutor tries to lock a job, and another tries this also. After acquiring the lock, they can execute it. But in this acquire phase you can expect to see the stale exceptions ...
This doesn't mean that there is something wrong. The JobExecutor is aware of these StaleExceptions and will act accordingly (ie leave the job alone for that moment). Unfortunately, this logrecord is created by Hibernate, which makes it hard to write code that doesn't throw this exception (if it is even possible) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215281#4215281 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215281 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
