Please report new issues athttps://github.com/DOCGroup
The ORB knows "well-known" multicast addresses for each well-known service. Unfortunately it re-uses the first one tried for subsequent servise resolutions. I think this is due to the implementation of TAO_ORB_Parameters which only has one multicast discovery endpoint variable instead of a sequence or map.
Can you provide an automated regression test for this one?
Wow, this is a very old issue! I don't recall raising this issue - I don't even remember trying the TAO multicast facilities. Is is possible Bugzilla has suffered a brain fart and someone else actually raised this one? I'm not currently working with ACE/TAO so am not in a position to even attempt a test case - sorry.
to pool