Hi, I'm finding that different components in Geode represent the member ID differently. For example, some MBeans might show the member as *10.118.33.250(server1:27254)<ec><v1>:1025* whereas the DistributionManager might show the member as *deppe-mbp(server1:27254)<ec><v1>:1025*.
Unfortunately there are (many?) places where member equivalency is tested by comparing the string representations. In this case, it fails. Do we have any code that checks equivalency based on the string representation of a member? I don't see anything in InternalDistributedMember. As an aside, there is some indication that this may only be relevant on Mac OS and not on Linux variants. Thanks --Jens
