]
Bela Ban resolved JGRP-825.
---------------------------
Fix Version/s: 3.5
(was: Future)
Resolution: Duplicate Issue
In 3.5, messages are looped back by default, so this issue is moot
Message: add a flag to discard own multicast
--------------------------------------------
Key: JGRP-825
URL:
https://issues.jboss.org/browse/JGRP-825
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 3.5
If we have a group consisting of members {A,B,C} and A wants to multicast to the group,
it will receive its own message too. To avoid this, A can set option LOCAL on its channel
to false, meaning that all messages sent by A will get discarded by A's channel.
The problem here is that those messages need to get handled nevertheless (e.g. by NAKACK,
including retransmissions), all the way up the stack, until they hit the channel - only to
be discarded there. This is a waste of resources (CPU and memory).
A solution is to discard the multicast at the transport level. If a message has a flag
LOCAL set to false, then TP discards it if
- the message is a multicast message and
- the sender of the message is the local member
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: