Aggregator meta data in properties
----------------------------------
Key: JBESB-2768
URL:
https://jira.jboss.org/jira/browse/JBESB-2768
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Content Based Routing
Affects Versions: 4.4 CP3
Reporter: Kevin Conner
Fix For: 4.4 CP4
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira