Bug 779887 (SOA-2246)

Summary: More then two correlated interactions on one operation cause process to hang.
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Marek Baluch <mbaluch>
Component: riftsawAssignee: trev <tkirby>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: urgent Docs Contact:
Priority: urgent    
Version: 5.1.0 Dev, 5.1.0.ER1   
Target Milestone: ---   
Target Release: 5.1.0 GA   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-2246
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-18 01:49:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Marek Baluch 2010-08-30 18:33:21 UTC
project_key: SOA

See linked issue.

Comment 1 Marek Baluch 2010-08-30 18:33:44 UTC
Link: Added: This issue depends RIFTSAW-278


Comment 2 Gary Brown 2010-09-07 15:58:50 UTC
Jeff has fixed the problem, so re-assigning to Marek to confirm and close.

Comment 4 Marek Baluch 2010-09-10 10:55:07 UTC
Invalid fix version.

Comment 5 Anne-Louise Tangring 2010-09-10 20:47:19 UTC
Candidate for SOA 5.1.0

Comment 6 trev 2010-09-14 13:40:12 UTC
Will resolve when we get the new version of riftsaw integrated

Comment 7 Marek Baluch 2010-10-01 09:09:45 UTC
Verified on ER2.

Comment 8 David Le Sage 2011-02-11 04:20:19 UTC
Temporarily reopening to update release notes.

Comment 9 David Le Sage 2011-02-11 04:25:38 UTC
Release Notes Docs Status: Added: Documented as Resolved Issue
Writer: Added: dlesage
Release Notes Text: Added: https://issues.jboss.org/browse/RIFTSAW-278

If the user had more than two "receive" activities on one operation then, upon the arrival of the third message, the process would fail to resume. This problem would also outlast the life of the process instance. This occurredbecause in the CorrelatorDAOImpl::removeLocalRoutes(...) used the processInstanceDAO object to make comparisons, resulting in a failure to delete the previous MessageRouteDAO. Hence, when the third message came in, it went via the same route as the second message. To resolve this issue, the software has been changed so that instanceID is now used to make the comparisons instead.


Comment 10 Dana Mison 2011-02-18 01:49:15 UTC
this is the first time we have shipped this so it does not have to be documented with resolved issues in the release notes

Comment 11 Dana Mison 2011-02-18 01:49:15 UTC
Release Notes Docs Status: Removed: Documented as Resolved Issue Added: Not Required