StaleObjectLog verbosity control code should be added to flushSession() ----------------------------------------------------------------------- Key: JBPM-1754 URL: https://jira.jboss.org/jira/browse/JBPM-1754 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Alejandro Guizar Fix For: jBPM 3.3.0 GA DbPersistenceService.flushSession line #272 Since a StaleObjectStateExcetion occures in flushSession() rather than commit(), StaleObjectLog verbosity control code should be added to flushSession() method as the same manner as commit(). See the following code snippet. An external transaction manager is being used and indeed DbPersistenceService.commit() does nothing. Exception flushSession() { if (mustSessionBeFlushed) { try { log.debug("flushing hibernate session " + session.toString()); session.flush(); // >>>>>>> begin } catch (StaleObjectStateException e) { log.info("optimistic locking failed"); StaleObjectLogConfigurer.staleObjectExceptionsLog.error("optimistic locking failed", e); return e; // <<<<<<< end } catch (Exception e) { log.error("hibernate flush failed", e); return e; } } return null; } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira