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. ------------------------------------------------------------------------------------------------------------------------------------
Link: Added: This issue depends JBESB-3309
Link: Added: This issue is related to SOA-2088
Link: Added: This issue related SOA-2223
Writer: Added: dlesage
Release Notes Docs Status: Added: Not Yet Documented
Link: Added: This issue is duplicated by SOA-2223
Temporarily reopening to update release note info.
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Resolved Issue Release Notes Text: Added: https://issues.jboss.org/browse/JBESB-3309 The MessageMulticaster created an aggregation identifier and stored this value in message properties. This caused problems when used in conjunction with the InVM transport because, when it was sent to multiple services all services would see the same properties and, depending on timing, potentially see the same aggregation identifier. To fix this problem, aggregation value is now stored in the message context as this section is always duplicated, rather than shared, when a reference is created.