Bug 779987 – ProcessLogs that represent changes of process intance that take place within Timer.Execute are not saved in DB

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 779987 - (SOA-2347) 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 ...

Status:	NEW

Aliases:	SOA-2347

Product:	JBoss Enterprise SOA Platform 5
Classification:	JBoss
Component:	JBPM - within SOA (Show other bugs)
Sub Component:
Version:	5.0.2
Hardware:	Unspecified Unspecified

Priority	high Severity high
Target Milestone:	---
Target Release:	FUTURE
Assigned To:	tcunning
QA Contact:
Docs Contact:

URL:	http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2010-09-27 09:02 EDT by Toshiya Kobayashi
Modified:	2018-03-29 17:46 EDT (History)
CC List:	3 users (show)

See Also:
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:	---

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

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
JBoss Issue Tracker	JBESB-3489	Major	Open	ProcessLogs that represent changes of process intance that take place within Timer.Execute are not saved in DB	2018-09-06 21:59 EDT
JBoss Issue Tracker	SOA-2347	Major	Closed	ProcessLogs that represent changes of process intance that take place within Timer.Execute are not saved in DB	2018-09-06 21:59 EDT

Groups: None (edit)

Description Toshiya Kobayashi 2010-09-27 09:02:30 EDT

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 09:03:30 EDT

Link: Added: This issue depends JBESB-3489

Comment 2 Kevin Conner 2010-10-01 15:21:35 EDT

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 15:35:43 EDT

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 15:50:37 EST

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

Comment 5 Suz 2012-06-15 01:08:02 EDT

    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-17 20:22:44 EDT

    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.

Note You need to log in before you can comment on or make changes to this bug.