[omniORB] omniNames4 fails where omniNames3 worked

[Donnacha Forde]

Platform Mix: 
Solaris 8
gcc 3.2.1
omniORB-4.0.0
java & client ORB = java1.4.0

I’ve upgraded from omniORB-3.0.4 to omniORB-4.0.0 and
my existing java client application now fails to
connect to omniNames. 

I use the following in the java client:

        props.put("org.omg.CORBA.ORBInitialPort",
"2809");
        props.put("org.omg.CORBA.ORBInitialHost",
"fred ");

where obviously, “fred” is the host where omniNames is
running. 

I connect with:

		org.omg.CORBA.Object objRef;
		
		try
		{
			objRef =
orb.resolve_initial_references("NameService");
		}

		catch (Exception e)
		{
			…

Now this all worked fine under omniORB-3.0.4 but is
throwing an exception with omniORB-4.0.0.
(org.omg.CORBA.OBJECT_NOT_EXIST)

I’ve had a peek at the trace output from omniNames and
it does appear to be contacted. One of more meaningful
output lines is:

omniORB: throw giopStream::CommFailure from
giopStream.cc:812(0,NO,COMM_FAILURE_UnMarshalArguments)


Any ideas or have you had this reported yet?

Regards, 
Donnacha


__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com