From daniel.kruegler at gmail.com Mon May 11 09:09:55 2026 From: daniel.kruegler at gmail.com (=?UTF-8?Q?Daniel_Kr=C3=BCgler?=) Date: Mon, 11 May 2026 11:09:55 +0200 Subject: [omniORB] Callbacks in an CORBA-SSL-only environment Message-ID: Hi, We are currently moving our CORBA server (Based on JacORB) towards an SSL-only configuration, i.e. we deactivate the regular CORBA port completely and allow only CORBA SSL (via ssliop). Our clients are based on OmniORB and we currently try to find an OmniORB configuration that works both for a CORBA server which supports (a) both plain CORBA and CORBA SSL and (b) only CORBA-SSL [To clarify: The expectation is, that the client is connecting via CORBA SSL, but should not know whether the server accepts either both CORBA SSL and plain CORBA or only CORBA SSL]. During my experiments I stumbled across the following issue when CORBA callbacks are involved (That is: The OmniORB client registers a callback on the JacORB server). Originally I had the following set in the OmniORB configuration: clientTransportRule = * ssl,unix,tcp,bidir serverTransportRule = * ssl,unix,tcp,bidir endPoint = giop:ssl:: = giop:tcp:: (A) My expectation was that under these client settings of endPoint giop:ssl::would be still preferred regardless of the server constraints, but that doesn't seem to hold. If the server is configured SSL-only, the client callback waits endlessly and is not called (without producing a CORBA connection error visible in the omniORB log file even under traceLevel=40. I found that it is required to set endPoint = giop:ssl:: to ensure that a client callback is called regardless whether the server is configured SSL-only or not. Is this behaviour expected and my chosen configuration the right one? What is the reason for this? (B) Then I tested the same scenario using unidirectional connection instead of bidirectional configuration (The POA construction was correspondingly adjusted programmatically), i.e. clientTransportRule = * ssl,unix,tcp serverTransportRule = * ssl,unix,tcp endPoint = giop:ssl:: Under these conditions the client callback never becomes called when being connected to a server configured as SSL-only. I'm wondering now, what kind of OmniORB setting is required to make callbacks work under such unidirectional conditions? Thanks for any hint, - Daniel -------------- next part -------------- An HTML attachment was scrubbed... URL: From msaied at EZZSteel.com.eg Mon May 11 09:13:03 2026 From: msaied at EZZSteel.com.eg (Mohamed Saied Essa Othman) Date: Mon, 11 May 2026 09:13:03 +0000 Subject: [omniORB] Callbacks in an CORBA-SSL-only environment In-Reply-To: References: Message-ID: unsubscribe EZDK-Business Disclaimer: This e-mail and any attachments are strictly confidential. If you are not the intended recipient: a) AL EZZ DEKHEILA STEEL COMPANY - ALEXANDRIA (EZDK) apologises but asks that you please immediately notify the sender and delete this e-mail from your system; and b) you must not copy or forward this e-mail or any attachments or disclose the contents to anyone, nor rely on information contained within the message. Statements and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of AL EZZ DEKHEILA STEEL COMPANY - ALEXANDRIA (EZDK). AL EZZ DEKHEILA STEEL COMPANY - ALEXANDRIA (EZDK) does not accept liability for any damage sustained as a result of software virus infection. We strongly recommend that you carry out your own virus check before opening any attachment. -------------- next part -------------- An HTML attachment was scrubbed... URL: