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

[Sai-Lai Lo]

dmorgen@alum.mit.edu (David Morgenlender) writes:
> 
> Problem solved ... I spoke with tech support for ETS Kernel ... they said
> to enable the structured exception capability.  Now exceptions work
> properly. 

Good news!

> 
> Now I have another problem.  When I run eg3_clt.exe, it reports:
> 
> 	Caught system exception COMM_FAILURE, unable to contact the object.
> 
> Here's my architecture:
> 
> 	ETS-Kernel:  	Corba server
> 
> 	Win95:	       	Name Service
> 			eg3_clt.exe
> 

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:0003ad4c0000000d49444c3a4563686f3a312e3000039414000000010000000000000028000100000000000e3135382e3132342e36342e363100e8300000000c3563f5176e0659ee00000001

And use catior on the output of nameclt:

% catior IOR:0003ad4c0000000d49444c3a4563686f3a312e3000039414000000010000000000000028000100000000000e3135382e3132342e36342e363100e8300000000c3563f5176e0659ee00000001
Type ID: "IDL:Echo:1.0"
Profiles:
1. IIOP 1.0 158.124.64.61 59440 "5c..n.Y....."
% 

Now, check in your case if the IP address is your server and the port
number looks alright.

You can even verify if the server is listen on that port:

$ telnet 158.124.64.61 59440

Good luck.

Sai-Lai

-- 
Dr. Sai-Lai Lo                          |       Research Scientist
                                        |
E-mail:         S.Lo@orl.co.uk          |       Olivetti & Oracle Research Lab
                                        |       24a Trumpington Street
Tel:            +44 223 343000          |       Cambridge CB2 1QA
Fax:            +44 223 313542          |       ENGLAND