[omniORB] Issue with firewalls

[Adnan Khan]

Duncan,

Thanks for getting back with me; I am on windows 2000 and setting config
parameters in the registry. Here is what my registry look like on the
server:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\omniORB]
"InitRef"="NameService=corbaname::10.1.1.62"
"acceptBiDirectionalGIOP"="1"
"traceLevel" = "40"
"traceInvocations" = "1"

[HKEY_LOCAL_MACHINE\SOFTWARE\omniORB\serverTransportRule]
"0"="* unix,tcp,bidir"

Any further thoughts will be much appreciated.

Thanks
Adnan


-----Original Message-----
From: Duncan Grisby [mailto:duncan at grisby.org]
Sent: Monday, February 16, 2004 5:49 AM
To: Adnan Khan
Cc: omniorb-list at omniorb-support.com; adaimee at proteligent.net
Subject: Re: [omniORB] Issue with firewalls


On Wednesday 11 February, "Adnan Khan" wrote:

> Thanks for getting back with me. I tried it based on the bidir example
comes
> with the distribution, however still it doesn't work. I saw that when I
turn
> on trace on the client I can see that it is creating "Bi-directional
> Connection" with the server.
>
> Client call to server->one_time() is successful
> Server fails to do client->call_back()
>
> I was wondering as to how can I see debug trace on the server side. I am
> setting traceInvocation=1 and traceLevel=40 in the config file but still
> unable to see any trace.

I don't know why you aren't seeing a trace. It should work fine. What
platform are you using?  Perhaps you should try setting the parameters
on the command line rather than the config file. In fact, maybe your
config file isn't working. That would explain why the bidir connection
isn't working too. Try specifying everything on the command line...

  bd_server -ORBtraceLevel 40 -ORBacceptBiDirectionalGIOP
1 -ORBserverTransportRule "* unix,tcp,bidir"

and then

  bd_client -ORBofferBiDirectionalGIOP 1 -ORBclientTransportRule "*
unix,tcp,bidir" IOR:...

In the server trace, you should see things like this:

...
omniORB: Accepted connection from giop:tcp:172.17.1.101:50027 because of
this rule: "* unix,tcp,bidir"
omniORB: inputMessage: from giop:tcp:172.17.1.101:50027 44 bytes
omniORB: Handling a GIOP LOCATE_REQUEST.
omniORB: sendChunk: to giop:tcp:172.17.1.101:50027 20 bytes
omniORB: inputMessage: from giop:tcp:172.17.1.101:50027 279 bytes
omniORB:  recieve codeset service context and set TCS to (ISO-8859-1,UTF-16)
omniORB:  receive bidir IIOP service context: ( 172.17.1.101:50026 )
omniORB: Accepted request from giop:tcp:172.17.1.101:50027 to switch to
bidirectional because of this rule: "* unix,tcp,bidir"
omniORB: Creating ref to remote: root/bidir<0>
 target id      : IDL:cb/CallBack:1.0
 most derived id: IDL:cb/CallBack:1.0
bd_server: Doing a single call-back: Hello!
omniORB: LocateRequest to remote: root/bidir<0>
omniORB: sendChunk: to giop:tcp:172.17.1.101:50027 44 bytes
...

Notice how the sendChunk for the LocateRequest to the callback object
is going to the same port number shown in the accepted connection.
That shows that it's using the same connection.

Cheers,

Duncan.

--
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --