[omniORB] [omniNames] no apparent communication

[Paul Fredrickson]

From: b.keeping@ic.ac.uk <b.keeping@ic.ac.uk>
Cc: omniorb-list@uk.research.att.com <omniorb-list@uk.research.att.com>

>Hi,
>
>Have you done as described in Configuration subsection 4 of README.UNIX?
>You don't mention which version of the cfg file you are using for
>example.
>

Well, I had gone through the readme, but it turns out I had assumed setting
OMNIORB_CONFIG was only necessary for omniNames itself.  When I set it in
the shell that started eg3_impl, instead of just aborting, it ended with a
COMM_FAILURE exception.

My omniORB.cfg contains only the NAMESERVICE IOR: blah blah blah, with
ORBInitialHost and ORBInitialPort set.  But upon closer inspection, I
noticed that the IOR in the cfg file didn't exactly match the string output
by omniNames when it started.  I'm not sure how that happened, since the one
in the config file was output automatically when I ran omniNames -start
1065.  As soon as I fixed the IOR in the config file, everything started
working fine.

Thanks for the pointers! It's working great now!

--Paul