[omniORB] VC++ 5: omniORB Mishandling Exceptions! Other errors!

David Morgenlender dmorgen@alum.mit.edu
Thu, 21 May 1998 12:49:50 GMT


Sai-Lai,

>> Now I have another problem.  When I run eg3_clt.exe, it reports:
>>=20
>> 	Caught system exception COMM_FAILURE, unable to contact the object.
>>=20
>> Here's my architecture:
>>=20
>> 	ETS-Kernel:  	Corba server
>>=20
>> 	Win95:	       	Name Service
>> 			eg3_clt.exe
>>=20
>
>This could be caused by a number of things. I suggest you first look at
>what the ETS server register with the Naming service.
>
>For instance, if the server register its object under the name
>   test,my_context/Echo,Object
>
>Use nameclt:
>$ nameclt resolve test my_context Echo Object
>IOR:0003ad4c0000000d49444c3a4563686f3a312e300003941400000001000000000000=
0028000100000000000e3135382e3132342e36342e363100e8300000000c3563f5176e065=
9ee00000001
>
>And use catior on the output of nameclt:
>
>% catior =
IOR:0003ad4c0000000d49444c3a4563686f3a312e3000039414000000010000000000000=
028000100000000000e3135382e3132342e36342e363100e8300000000c3563f5176e0659=
ee00000001
>Type ID: "IDL:Echo:1.0"
>Profiles:
>1. IIOP 1.0 158.124.64.61 59440 "5c..n.Y....."
>%=20
>
>Now, check in your case if the IP address is your server and the port
>number looks alright.

catior comes up with an ASSERTION failure when I do this.  This is what's
printed until that point (nothing else is printed if I say to ignore the =
error):

	Type ID: "IDL:Echo:1.0"
	Profiles:
	1. IIOP 1.0 127.0.0.1 0 "5b.\........"

That's not the IP address of the ETS-Kernel box!

How do I correct that?

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
Dave Morgenlender
e-mail: dmorgen@alum.mit.edu
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D