[jbpm-issues] [JBoss JIRA] Resolved: (JBPM-1992) Logging is missing if JobExecutorThread marks TX as rollbackonly because of max
[
https://jira.jboss.org/browse/JBPM-1992?page=com.atlassian.jira.plugin.sy...
]
Alejandro Guizar resolved JBPM-1992.
------------------------------------
Fix Version/s: (was: jBPM 3.2.x)
Resolution: Out of Date
Between SOA-1998 and JBPM-2861 JobExecutorThread no longer rolls back completed jobs that
have been locked too long. Resolution of such conflicts is now delegated to the
persistence framework (optimistic control) or the database (pessimistic locks). Given that
the transaction started by the JobExecutorThread will be older than the
LockMonitorThread's, it is expected that the job execution will complete successfully
and the overdue jobs unlock will fail in case of a conflict.
Logging is missing if JobExecutorThread marks TX as rollbackonly
because of max
-------------------------------------------------------------------------------
Key: JBPM-1992
URL: https://jira.jboss.org/browse/JBPM-1992
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 3.3.1 GA
Reporter: Roman Heinz
If the execution of an action/script/... takes longer than the time configured
org.jbpm.job.executor.JobExecutor.maxLockTime, the current TX is marked as rollback-only
without any logging.
In JobExecutorThread:
// if this job is locked too long
long totalLockTimeInMillis = System.currentTimeMillis() -
job.getLockTime().getTime();
if (totalLockTimeInMillis>maxLockTime) {
jbpmContext.setRollbackOnly();
}
Logging is missing to inform about the jbpmContext.setRollbackOnly() together with the
reason.
Otherwise you'll see the same Job running again and again without an obvious reason
for the rollback.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira