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

[David Morgenlender]

Sai-Lai,

Problem solved ... I spoke with tech support for ETS Kernel ... they said=
 to
enable the structured exception capability.  Now exceptions work =
properly.  I
looked in the manuals under "exception" & saw nothing about this.  The =
link
files state this is for structured exceptions, not mentioning C++ =
exceptions.
IAE, it solved the problem.

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

I used my same code to build a Win32 console app.  When I run it under =
the
following architecture it works:

	Win95:	       	Name Service
			eg3_clt.exe
			Corba server

The server running under ETS-Kernel presumably registered with the Name =
Service
successfully, since it reported no errors.  I confirmed it called & =
stayed in
boa->impl_is_ready().  This code is almost identical to eg3_impl.

Do you have any idea what could be going on or where I should look?  Are =
eg3_clt
& eg3_impl designed to be run on different systems?

IAE, it seems like I'm getting close!

=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