[
https://issues.jboss.org/browse/JGRP-1823?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1823:
--------------------------------
[~dan.berindei] So you have \{A,B,C\}, and A invokes an RPC that should exclude itself ?
The change afaics is that you *don't* use the exclusion list to exclude A, but set the
DONT_LOOPBACK flag ?
That's IMO an incorrect use of DONT_LOOPBACK... However, as the correct use would
force you to use the DONT_LOOPBACK flag *and* an exclusion list, I'll optimize the
exclusion list away.
SOLUTION:
If DONT_LOOPBACK is set, remove the sender's address from {{real_dests}}.
MessageDispatcher expects a response from the local node with
DONT_LOOPBACK
---------------------------------------------------------------------------
Key: JGRP-1823
URL:
https://issues.jboss.org/browse/JGRP-1823
Project: JGroups
Issue Type: Bug
Affects Versions: 3.5
Reporter: Dan Berindei
Assignee: Bela Ban
Fix For: 3.5
MessageDispatcher doesn't remove the local node from the `real_dests` collection when
using DONT_LOOPBACK, and that causes RPCs broadcasted to the entire cluster to time out.
--
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:
http://www.atlassian.com/software/jira