[infinispan-issues] [JBoss JIRA] (ISPN-4190) Use Message.Flag.DONT_LOOPBACK instead of RequestOptions.setExclusionList

William Burns (JIRA) issues at jboss.org
Mon May 12 11:19:57 EDT 2014


     [ https://issues.jboss.org/browse/ISPN-4190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

William Burns reopened ISPN-4190:
---------------------------------



The first pass at this didn't quite work out.  However a newer version of JGroups should allow this to work with the fix included in JGRP-1835.

> Use Message.Flag.DONT_LOOPBACK instead of RequestOptions.setExclusionList
> -------------------------------------------------------------------------
>
>                 Key: ISPN-4190
>                 URL: https://issues.jboss.org/browse/ISPN-4190
>             Project: Infinispan
>          Issue Type: Task
>          Components: Core
>    Affects Versions: 7.0.0.Alpha2
>            Reporter: Dan Berindei
>            Assignee: Dan Berindei
>             Fix For: 7.0.0.Alpha4
>
>
> We are currently using {{RequestOptions.setExclusionList(channel.getAddress())}} in CommandAwareRpcDispatcher, to prevent the sender of an RPC to receive that message. We can't use {{Channel.setDiscardOwnMessages(true)}}, because TO requires messages to be delivered to self.
> JGroups 3.5.0.Beta2 has added a {{DONT_LOOPBACK}} flag, which should be a lot more efficient than using the exclusion list. We should start using it.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)


More information about the infinispan-issues mailing list