[omniORB] omniORB's naming service promotes suicidal ideations

[Clarke Brunt]

>The C++, VB and Java clients talk to the Java and VB servers
interchangeably.. yay. However the C++ (omniORB) client is the only client
that can talk to the C++ server! This has led me to believe that a
misconfiguration of the omniORB naming service daemon is probably the prime
cause of the Java and VB clients inability to contact the C++ server.

>I'm begging anyone out there if they have got other ORBs to work with
omniORB  to please PLEASE send me their omniORB.cfg and omniNames.cfg files
so that I might be able to gain some insight on what I am doing wrong. Dont
make me write this server with Java :(

Things you might need to check:

omninames -ORBsupportBootstrapAgent 1
allows omninames to support a bootstrap protocol using by the Sun Java ORB
to resolve initial references. This option used to be the default in
OmniORB3, but not in 4.

If this then allows you to resolve names, but things still don't work, then
check
-ORBmaxGIOPVersion 1.0
on the command line for your server (or in the .cfg, presumably without
the -ORB at the start). Some versions (possibly even the latest version?) of
the Sun Java ORB don't like GIOP 1.2 used by default by OmniORB4.

--
Clarke Brunt, Principal Software Engineer, Yeoman Navigation