[omniORB] COMM_FAILURE recieved when connecting to omni server

[Shibu Mathai]

We are unable to connect to the omni server running on App Machine from DB
Machine the . We tested using nameclt and the output is shown below it's
gives a COMM_FAILURE. Could anyone please help.

[***@fms-db sys]$ nameclt -ORBInitialHost 10.0.91.129 -ORBInitialPort
14285 -ORBtraceLevel 100 list
strand Ripper: start.
scavenger : start.
gateKeeper is tcpwrapGK 1.0 - based on tcp_wrappers_7.6
strand Rope::incrRefCount: old value = 0
strand Rope::decrRefCount: old value = 1
strand Rope_iterator: delete unused Rope.
tcpSocketMTfactory ~tcpSocketOutgoingRope: called
strand Rope::incrRefCount: old value = 0
omniORB: Getting initial object reference for NameService from
'IOR:01000000240000006f6d672e6f72672f434f5242412f496e697469616c5265666572656e6365733a312e3000010000000000000020000000010100000c00000031302e302e39312e31323900cd374e6104000000494e4954'...ll_send:
68 bytes
4749 4f50 0100 0100 3800 0000 0000 0000 GIOP....8.......
0100 0000 0100 0000 0400 0000 494e 4954 ............INIT
0400 0000 6765 7400 0700 0000 6e6f 626f ....get.....nobo
6479 0000 0c00 0000 4e61 6d65 5365 7276 dy......NameServ
6963 6500 ice.
ll_recv: 116 bytes
4749 4f50 0100 0101 6800 0000 0000 0000 GIOP....h.......
0100 0000 0000 0000 2800 0000 4944 4c3a ........(...IDL:
6f6d 672e 6f72 672f 436f 734e 616d 696e omg.org/CosNamin
672f 4e61 6d69 6e67 436f 6e74 6578 743a g/NamingContext:
312e 3000 0100 0000 0000 0000 2400 0000 1.0.........$...
0101 0000 0a00 0000 3132 372e 302e 302e ........127.0.0.
3100 cd37 0c00 0000 44c7 4b5d 7deb c656 1..7....D.K]}..V
0000 0002 ....
strand Rope::incrRefCount: old value = 0
Done CORBA::InitialReferences::get().
tcpSocketMTfactory ~tcpScoketStrand: close socket no. -1
list: Cannot contact the Naming Service because of COMM_FAILURE.
strand Rope::decrRefCount: old value = 1
omniORB: WARNING - Proxy object not released.
IR ID : IDL:omg.org/CosNaming/NamingContext:1.0
RefCount: 2
ObjRef :
IOR:010000002800000049444c3a6f6d672e6f72672f436f734e616d696e672f4e616d696e67436f6e746578743a312e3000010000000000000024000000010100000a0000003132372e302e302e3100cd370c00000044c74b5d7debc65600000002
scavenger : woken by poke()
scavenger : exit.
strand Ripper: exit.
strand Rope::decrRefCount: old value = 1

Regards
Shibu Mathai

[Duncan Grisby]

Post by Shibu Mathai
We are unable to connect to the omni server running on App Machine from DB
Machine the . We tested using nameclt and the output is shown below it's
gives a COMM_FAILURE. Could anyone please help.

In future, it is a good idea for you to mention the omniORB version you
are using. You are clearly using 3.0 or something even older.

What's going wrong is that although you are contacting the correct
server to talk to its bootstrap agent, the server is replying with an
object reference that says the IP address to use is 127.0.0.1. When the
client tries to use that, it tries to connect to itself, and of course
fails.

The server is misconfigured, probably because it has an /etc/hosts file
that maps the server's name to 127.0.0.1. You need to fix it to have the
correct address, or to upgrade to omniORB 4.0 which uses a different
mechanism to determine its IP address.

Cheers,

Duncan.