Please report new issues athttps://github.com/DOCGroup
The IMR currently only supports a single IIOP profile in an IOR. However, once TAO's support for hosts with multiple network interfaces is committed an endpoint will be created on each interface for the default case `-ORBEndpoint iiop://'. The generated IOR will contain a profile for each endpoint. The IMR should be able to handle such an IOR. Note, that updates to the IORManipulation class may be needed to make this task easier.
I don't think this is as high of a priority, as long as the default works. A lot depends on whether the multiple endpoints can be represented in one string, since the IMR stores the servers endpoint as one string. It then takes the endpoint and attaches the object key to it. So if we are able to say something like: iiop://ringil:5000;ringil:5001/object then it shouldn't be a problem.
Just a clarification... The iioploc URL format (not "iiop" :-) supports multiple addrs in the IOR, e.g.: iioploc://1.1@ringil:1234,1.0@ringlebells/objkey However, since we support protocols other than IIOP in an IOR, creating a signle URL style IOR that contains mixed protocols is not possible. Does the forthcoming "corbaloc" format support this?
Darrell is no longer responsible for the ImR.
Accepting for tao-support
Accepted.
Steve, can OCI check this one?
As far as I can tell, this is still an issue.
I believe this bug relates to the stored partial IOR used by the ImR to synthesize a corbaloc string as the foward-to target. The server composes the partial IOR using the stub's "profile_in_use" value, which limits it to a single profile. That profile may have alternate addresses though.