[omniORB] getObjectRef fail

Duncan Grisby duncan at grisby.org
Thu Oct 10 09:10:36 BST 2013


On Wed, 2013-10-09 at 00:35 +0530, sheena kansal wrote:
> here are the more traces showing object was registered earlier, that
> later start failing:

Your traces are very hard to follow. It would be extremely helpful if
you included the omniORB startup messages so it was possible to see its
configuration. It would also be helpful if you could produce a trace of
just omniORB's messages without the extra stuff added by your logging
code.

[...]
> omniORB: (?) sendChunk: to
> giop:unix:/tmp/forb.socket.fsp.local.omninames 100 bytes

That shows that you have (presumably) managed to configure omniNames to
use a Unix domain socket...

> 00000029.397108288| 1522|FWDBORB         | 308|
> 00000029.397186852| 1522|FWDBORB         | 308|I>[fwdbServLogger]
> omniORB: (?)
> 00000029.397186852| 1522|FWDBORB         | 308|4749 4f50 0102 0000
> 0000 0058 0000 0012 GIOP.......X....

[...]
>  omniORB: (?) Switch rope to use address
> giop:tcp:[6C:AE:8B:6E:00:36]:0

But the connection to the unix socket failed, and it's now trying to use
another endpoint in the object reference, but it is invalid. It looks
superficially like an IPv6 address, but it has insufficient bytes, and
it specifies invalid port 0 anyway.

> 00000029.397367626| 1523|FWDBORB         | 308|
> 00000029.397625158| 1523|FWDBORB         | 308|I>[fwdbServLogger]
> omniORB: (?) Client connection refcount = 0
> 00000029.397625158| 1523|FWDBORB         | 308|
> 00000029.397635688| 1523|FWDBORB         | 308|I>[fwdbServLogger]
> omniORB: (?) Client close connection to
> giop:unix:/tmp/forb.socket.fsp.local.omninames
> 00000029.397635688| 1523|FWDBORB         | 308|
> 00000029.397994482| 1523|FORB            |  87|Caught CORBA::TRANSIENT
> handleExceptions:190

Because the connection to the unix socket failed and the only other
endpoint was invalid, you get a TRANSIENT exception with minor code
TRANSIENT_ConnectFailed.

Something is missing in your logging because omniORB would have logged
that it was throwing the exception, but it's missing from the trace.

Whatever odd thing happened, it looks like omniNames went away. Did it?

Duncan.

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





More information about the omniORB-list mailing list