Bug 779987 (SOA-2347)

Summary:	ProcessLogs that represent changes of process intance that take place within Timer.Execute are not saved in DB
Product:	[JBoss] JBoss Enterprise SOA Platform 5	Reporter:	Toshiya Kobayashi <tkobayas>
Component:	JBPM - within SOA	Assignee:	tcunning
Status:	NEW ---	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	5.0.2	CC:	rwagner
Target Milestone:	---
Target Release:	FUTURE
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-2347
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	When using jBPM, ProcessLogs (which represent changes of the process instance within Timer.Execute) are not saved in the database.	Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Toshiya Kobayashi 2010-09-27 13:02:30 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 ProcessLogs that represent changes of process intance that take place within Timer.Execute are not saved in DB

Comment 1 Kevin Conner 2010-09-27 13:03:30 UTC

Link: Added: This issue depends JBESB-3489

Comment 2 Kevin Conner 2010-10-01 19:21:35 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 3 Kevin Conner 2010-10-01 19:35:43 UTC

Sorry, SOA-2344 is the 5.1 task, this is a place holder in case there is another 5.0 task.

Comment 4 Rick Wagner 2011-12-05 20:50:37 UTC

Rick reviewing old JIRAs.  JBESB-3489 still open, looks valid.  Left open.

Comment 5 Suz 2012-06-15 05:08:02 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
When using JBPM, ProcessLogs representing changes of the process instance within Timer.Execute are not saved in the database.

Comment 6 David Le Sage 2012-06-18 00:22:44 UTC

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-When using JBPM, ProcessLogs representing changes of the process instance within Timer.Execute are not saved in the database.+When using jBPM, ProcessLogs (which represent changes of the process instance within Timer.Execute) are not saved in the database.