-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: 4.9
-
Fix Version/s: 4.9 CP1
-
Component/s: Process flow
-
Labels:None
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);
- blocks
-
SOA-2344 ProcessLogs that represent changes of process intance that take place within Timer.Execute are not saved in DB
-
- Closed
-
- relates to
-
JBESB-3489 ProcessLogs that represent changes of process intance that take place within Timer.Execute are not saved in DB
-
- Open
-
-
JBESB-3490 ProcessLogs that represent changes of process intance that take place within Timer.Execute are not saved in DB
-
- Open
-
-
JBPM-1015 ProcessLogs that represent changes of process intance that take place within Timer.Execute are not saved in DB
-
- Closed
-