[ https://jira.jboss.org/jira/browse/JGRP-882?page=com.atlassian.jira.plugi... ] Bela Ban updated JGRP-882: -------------------------- Attachment: bla.java Modify bla to point to the correct single.xml -- 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

[ https://jira.jboss.org/jira/browse/JGRP-882?page=com.atlassian.jira.plugi... ] Bela Ban updated JGRP-882: -------------------------- Attachment: single.xml -- 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

[ https://jira.jboss.org/jira/browse/JGRP-882?page=com.atlassian.jira.plugi... ] Vladimir Blagojevic updated JGRP-882: ------------------------------------- Summary: Shared transport: promiscuous discovery requests with MPING (was: Shared transport: promiscuous discovery requests with TCP) This issue is unrelated to TCP or transport used but rather it is directly related to MPING. Since 2.7 we have a cluster_name that allows TP to route to appropriate stack in shared transport. However, in MPING discovery messages bypass transport protocol and are sent directly to network interface thus causing interference. -- 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

[ https://jira.jboss.org/jira/browse/JGRP-882?page=com.atlassian.jira.plugi... ] Vladimir Blagojevic commented on JGRP-882: ------------------------------------------ This issue is unrelated to TCP or transport used but rather it is directly related to MPING. Since 2.7 we have a cluster_name that allows TP to route messages to appropriate stack in shared transport. However, in MPING discovery messages bypass transport protocol and are sent directly to network interface with appropriate mcast address and port thus causing interference. -- 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

[ https://jira.jboss.org/jira/browse/JGRP-882?page=com.atlassian.jira.plugi... ] Vladimir Blagojevic updated JGRP-882: ------------------------------------- Workaround Description: Select different mcast address and port address per stack on shared transport. For example, all A channels on different shared transports should have the same MPING mcast_addr and port combination that is unique and different from all B channels on different shared transports. -- 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