[jboss-jira] [JBoss JIRA] (JGRP-1765) TP: enable loopback by default and discard own multicasts

[Bela Ban (JIRA)]

    [ https://issues.jboss.org/browse/JGRP-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12950543#comment-12950543 ] 

Bela Ban commented on JGRP-1765:
--------------------------------

Perhaps we can get rid of the copy of the message when looping it back up. However, we need to take care of concurrent access to the headers, e.g. when the message is sent down on the original thread, headers may get added, but the newly spawned thread looping the message back up might access the headers at the same time. The headers (Headers) are not synchronized.
                
> TP: enable loopback by default and discard own multicasts
> ---------------------------------------------------------
>
>                 Key: JGRP-1765
>                 URL: https://issues.jboss.org/browse/JGRP-1765
>             Project: JGroups
>          Issue Type: Enhancement
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>             Fix For: 3.5
>
>
> Enable {{TP.looback}} by default (deprecate and ignore prop): all messages sent by self are passed right to a thread pool to send them up again.
> When a multicast message sent by self is received, it is currently passed to a thread pool, de-serialized and only then discarded if loopback=true. This means that we create an unneeded buffer for de-serializationand perform de-serialization.
> SOLUTION: discard the multicast from self immediately when receiving it, in {{TP.receive()}}

--
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