[
https://jira.jboss.org/jira/browse/JGRP-921?page=com.atlassian.jira.plugi...
]
Bela Ban updated JGRP-921:
--------------------------
Fix Version/s: (was: 2.6.9)
2.6.x is NOT affected because we add the right header in TP.ProtocolAdapter already.
TP.down() checks if a header is already present and doesn't add a header if yes
TP: 'header' is ambiguous with shared transport
-----------------------------------------------
Key: JGRP-921
URL:
https://jira.jboss.org/jira/browse/JGRP-921
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 2.8
TP.header is created on down(CONNECT). However if we have members A and B on the *same
shared transport*, then A.connect("cluster-1") sets TP.header to
"cluster-1", but B.connect("cluster-2") sets TP.header to
"cluster-2".
This means that messages sent by A will get received by B !!
Investigate whether this was introduced by logical addresses only, or whether it affects
2.6.x as well !
--
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