Closed aegsgm closed 7 months ago
Further to the above issue, I have used the -ORBListenEndpoint, so that the static IP will get embedded in the IOR. Then, the code breaks while processing the lifetime policy. Is there any idea to proceed with the issue ? Will it help if I try CosNaming to resolve the corbaloc issue ?
@jwillemsen Can you please help on this ?
Thanks, Aegsgm
All support on github is best effort, if you want guaranteed support, see https://github.com/DOCGroup/ACE_TAO/wiki/ACE-and-TAO-Commercial-support, that also lists @RemedyIT for which I work, through that company I can assist you with ACE/TAO directly.
@jwillemsen Looks like SSL is not supported when using corbaloc/Impl repo.
Can someone please answer my query and confirm if we can implement SSL on Top of Implementation Repository configuration as I am facing an exception when implementing lifespan policy to persist objects. Or, please suggest whether I need to configure any new policies specific to SSL ?
Thanks in advance.
Regards, Aegsgm
Without SSL, The Impl repo works just fine using a CORBALOC.
Experimented, by implementing SSL is on top of this setup. The connection with server was successful from client when passing the IOR as string to string_to_object function. The object is constructed & able to communicate with server.
But the same setup fails, when I try to get server object by passing a CORBALOC string from client.
So, decided to find the difference between IOR & CORBALOC.
I have decoded the IOR using tao_catior.exe.
and found that the tagged SSL component was having different port during every start. Further validated the connection by using the new port decoded from IOR in the CORBALOC which connected successfully.
Why the port number is randomly changed in IOR when implementing SSL?.
Is it expected behavior when using SSL with SSL repo?
-Aegsgm