[
https://jira.jboss.org/browse/JBESB-3487?page=com.atlassian.jira.plugin.s...
]
Kevin Conner commented on JBESB-3487:
-------------------------------------
The ESB version of this (using JCA inflow) copies and replaces the 'enterprise'
codebase from jBPM, and not the JobExecutorThread variant. It looks like this fix never
made it into that codebase.
ProcessLogs that represent changes of process intance that take place
within Timer.Execute are not saved in DB
--------------------------------------------------------------------------------------------------------------
Key: JBESB-3487
URL:
https://jira.jboss.org/browse/JBESB-3487
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Process flow
Affects Versions: 4.9
Reporter: Toshiya Kobayashi
Log events won't be saved when they are triggered by Timer.
This issue was fixed in JobExecutorThread ( JBPM-1015 ). But regarding SOA integration,
only org.jboss.soa.esb.services.jbpm.integration.job.ExecuteJobCommand includes the fix.
org.jboss.soa.esb.services.jbpm.integration.job.ExecuteTimerCommand should follow.
# Snippet from org.jboss.soa.esb.services.jbpm.integration.job.ExecuteJobCommand
// register process instance for automatic save
// see
https://jira.jboss.org/jira/browse/JBPM-1015
ProcessInstance processInstance = job.getProcessInstance();
jbpmContext.addAutoSaveProcessInstance(processInstance);
--
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