Bug 779726 (SOA-2088)

Summary: Aggregator meta data in properties
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Stelios Koussouris <skoussou>
Component: JBossESBAssignee: tcunning
Status: NEW --- QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.3 CP02CC: rwagner
Target Milestone: ---   
Target Release: FUTURE   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-2088
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
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:

Description Stelios Koussouris 2010-05-20 11:34:21 UTC
Affects: Documentation (Ref Guide, User Guide, etc.), Interactive Demo/Tutorial
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 Stelios Koussouris 2010-05-20 11:35:08 UTC
Link: Added: This issue depends JBESB-2768


Comment 2 Stelios Koussouris 2010-05-20 11:35:40 UTC
Link: Added: This issue incorporates JBESB-3310


Comment 3 Kevin Conner 2010-08-09 15:26:16 UTC
Link: Added: This issue related SOA-2215


Comment 4 Kevin Conner 2010-08-09 15:27:16 UTC
Link: Removed: This issue incorporates JBESB-3310 


Comment 5 Rick Wagner 2011-12-05 20:54:36 UTC
Rick reviewing old JIRAs.  Recently revisited, seems valid. The Aggregator is troublesome anyway, leaving Open.