[omniORB] OmniORB 4.1.4 bidirectional GIOP fails

[mbazs123]

Duncan Grisby wrote:
> 
> 1980 is the port the JacORB side is listening on as a server. It is the
> address stored in object references coming from JacORB, and thus the
> address the server should use for callbacks to your client if
> bidirectional is not in use.
> 
> The way bidirectional GIOP works is that the client sends a message
> saying that whenever the server makes an invocation on an object
> reference with the specified endpoint details (in this case
> 192.168.0.143:1980), the call should instead go through the incoming
> connection (in this case port 1982). To avoid a security issue where a
> client can hijack calls intended for a completely different server, the
> only object references that are candidates for bidirectional calls are
> ones that have passed through the connection in question.
> 

So you're saying that on client side (Jacorb) everything OK with the
bidirectional settings?
Good news! :)


Duncan Grisby wrote:
> 
> So, the question is why your object reference was not handled correctly.
> How did the server get the callback reference?  One guess is that it was
> passed as a string, rather than as an object reference, meaning that
> omniORB did not know the reference came through the connection. Could
> that be it?
> 

My client calls a server-side factory operation, passing a callback object
as one of the parameters. So I don't mess with string IORs etc.

What is very weird for me is that it is really doing what you've said, but
it seems omniORB cannot map the port found in "IIOP service context" to the
good, alive incoming socket. I'm seeing in 'netstat' that the 'good' channel
is very OK. So I don't really understand this ...

Of course I've done this, too:

const char *options[][2]={
    {"serverTransportRule","* tcp,ssl,bidir"},
    {"acceptBiDirectionalGIOP","1"},
    {0,0}};
try {
    m_orb=CORBA::ORB_init(argc,argv,"omniORB4",options);

Anyway, thx 4 the answer!
MB



-- 
View this message in context: http://old.nabble.com/OmniORB-4.1.4-bidirectional-GIOP-fails-tp28732899p28743156.html
Sent from the OmniORB - User mailing list archive at Nabble.com.