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

[Sai-Lai Lo]

>>>>> David Morgenlender writes:

> "OMNIORB_USEHOSTNAMEVAR" turns out to be the #define in the code.
> "OMNIORB_USEHOSTNAME" is the environment variable.  

My apology! Arne was right.

> So I set it to "Target" on
> the server (ETS-Kernel) system.  Then I set "Target" to the ETS system's IP
> address in the "hosts" file in my Win95 directory (client system).

> Unfortunately, I still get the COMM_FAILURE from eg3_clt.exe.  The catior
> output:

> catior IOR:012ccb000d00000049444c3a4563686f3a312e3000000000010000000000000024000
> 000010100000700000054617267657400cd0000cdcd0c0000003565476d0000101400000001
> Type ID: "IDL:Echo:1.0"
> Profiles:
> 1. IIOP 1.0 Target 0 "5eGm........"

Hm! Why is the port number 0? This can't be right. Is there something wrong
with your machine setup? Your last printout has a more sensible value.

I think you are getting close. 

If you manage to get your server to emit an IOR with say Target and port x
(x != 0), try "telnet Target x". If you've connected successfully, type a
few keys randomly until the server shut you off with a GIOP close
connection message. If you are able to do this, we have to look into what
goes on at eg3_clt.exe. What you can do then is to try eg2_clt and gives
the IOR as its argument to see if the COMM_FAILURE is actually cause by
eg3_clt's communication with the naming service.

Happy debugging.

Sai-Lai