[jbpm-issues] [JBoss JIRA] Updated: (JBPM-1992) Logging is missing if JobExecutorThread marks TX as rollbackonly because of max
[
https://jira.jboss.org/jira/browse/JBPM-1992?page=com.atlassian.jira.plug...
]
Roman Heinz updated JBPM-1992:
------------------------------
Description:
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.
was:
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.
Logging is missing if JobExecutorThread marks TX as rollbackonly
because of max
-------------------------------------------------------------------------------
Key: JBPM-1992
URL: https://jira.jboss.org/jira/browse/JBPM-1992
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core 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/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira