Bug 779984 (SOA-2344) - ProcessLogs that represent changes of process intance that take place within Timer.Execute are not saved in DB
Summary: ProcessLogs that represent changes of process intance that take place within ...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2344
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBPM - within SOA
Version: 5.1.0.ER1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.1.0 GA
Assignee: Kevin Conner
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-24 10:13 UTC by Toshiya Kobayashi
Modified: 2011-02-11 03:41 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-11 03:41:35 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2344 0 None None None Never

Description Toshiya Kobayashi 2010-09-24 10:13:20 UTC 
Affects: Release Notes
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000003kJYX&sfdc.override=1
project_key: SOA

Platform JIRA for [JBESB-3487] ProcessLogs that represent changes of process intance that take place within Timer.Execute are not saved in DB
Comment 1 Kevin Conner 2010-10-01 19:36:16 UTC 
I am going to investigate this for 5.1 as it may be a simple fix. We now have a test which demonstrates the issue.
Comment 2 Kevin Conner 2010-10-11 12:27:51 UTC 
Link: Added: This issue depends JBESB-3487
Comment 4 Dana Mison 2011-01-05 00:14:29 UTC 
Writer: Added: dlesage
Comment 5 David Le Sage 2011-02-11 03:36:53 UTC 
Temporarily reopening to update the release note info.
Comment 6 David Le Sage 2011-02-11 03:41:26 UTC 
Release Notes Docs Status: Added: Documented as Resolved Issue
Release Notes Text: Added: https://issues.jboss.org/browse/JBESB-3487

The process logs that recorded changes in process instances within Timer.Execute were not being saved in the database.  To fix this problem, a code change has been made to ExecuteTimerCommand.java.  As a result, the JBPM_LOG table now shows entries for the variable modification and transitions from the timer.
Note You need to log in before you can comment on or make changes to this bug.