Bug 779856 (SOA-2216) - bpm_orchestration2 process is not safe
Summary: bpm_orchestration2 process is not safe
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2216
Deadline: 2010-03-08
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB, Examples
Version: 5.0.0 GA
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-08-09 15:42 UTC by Len DiMaggio
Modified: 2011-02-17 11:30 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-17 11:30:19 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 779108 0 high NEW bpm_orchestration2 process is not safe 2021-10-15 11:51:54 UTC
Red Hat Issue Tracker SOA-2216 0 Major Closed bpm_orchestration2 process is not safe 2012-11-04 13:21:50 UTC

Internal Links: 779108

Description Len DiMaggio 2010-08-09 15:42:20 UTC 
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/303315
project_key: SOA
Comment 1 Kevin Conner 2010-08-09 15:43:09 UTC 
Link: Added: This issue is related to SOA-1507
Comment 2 Kevin Conner 2010-08-09 15:44:32 UTC 
Link: Added: This issue depends JBESB-3450
Comment 3 Anne-Louise Tangring 2010-09-10 16:29:14 UTC 
This is a candidate for SOA 5.1.
Comment 4 Laura Bailey 2010-12-17 00:41:28 UTC 
Writer: Added: Darrin
Comment 5 Laura Bailey 2010-12-17 00:47:58 UTC 
Release Notes Docs Status: Added: Not Yet Documented
Comment 7 Len DiMaggio 2011-01-06 19:48:59 UTC 
Verified in ER6 build.
Comment 8 Dana Mison 2011-02-17 11:30:19 UTC 
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Resolved Issue
Labels: Removed: rn-dmison rn-open 
Release Notes Text: Added: The bpm_orchestration2 quickstart used to demonstrate fork and join operations in the business process could result in contention between the forked actions.  This was because the forked actions were all configured to update the same process variable.  This quickstart has been updated so that the forks use different variables.  This prevents the contention with actions after the join responsible for merging the data
Note You need to log in before you can comment on or make changes to this bug.