Bug 779864 (SOA-2223)

Summary: Aggregator meta data in properties
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Stelios Koussouris <skoussou>
Component: JBossESBAssignee: Kevin Conner <kevin.conner>
Status: CLOSED DUPLICATE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.0.0 GA   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-2223
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-08 23:02:18 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 Stelios Koussouris 2010-08-10 16:24:10 UTC
Affects: Interactive Demo/Tutorial, Documentation (Ref Guide, User Guide, etc.)
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&tid=864653&gid=1354
project_key: SOA

------------------------------------------------------------------------------------------------------------------------------------
The MessageMulticaster creates an aggregation id and stores this value in message properties. Normally this does not prove to be an issue but when using invm transport it may cause issues.

When the message is sent to multiple services, using pass by reference semantics, then all services will see the *same* properties and may, depending on timing, see the same aggregation id.

The aggregation value should really be in the message context as this section is always duplicated when creating a reference, never shared. The problem we face is that users may already be referencing the property, especially if they are creating a fresh response message, so we need to think about handling this.
------------------------------------------------------------------------------------------------------------------------------------

Comment 1 Kevin Conner 2010-08-10 16:24:50 UTC
Link: Added: This issue is related to SOA-2215


Comment 2 Kevin Conner 2010-08-10 16:25:54 UTC
Link: Added: This issue depends JBESB-3310


Comment 3 Kevin Conner 2010-08-10 16:36:10 UTC
Link: Added: This issue is incorporated by SOA-2210


Comment 4 Kevin Conner 2010-08-17 16:48:29 UTC
Link: Added: This issue depends JBESB-3464


Comment 5 Laura Bailey 2010-12-17 00:41:33 UTC
Writer: Added: Darrin


Comment 6 Laura Bailey 2010-12-17 00:47:57 UTC
Release Notes Docs Status: Added: Not Yet Documented


Comment 8 Kevin Conner 2011-02-08 23:01:49 UTC
This is now a duplicate of SOA-2215

Comment 9 Kevin Conner 2011-02-08 23:01:49 UTC
Link: Added: This issue duplicates SOA-2215