[omniORB] omniNames4 fails where omniNames3 worked

Thu Jan 30 15:12:02 2003

The default configuration of omniORB4 turns off the bootstrap agent feature
that you're trying to utilize from your Java client.  It was on in omniORB3
by default.  Read the comments in the omniORB4 example config file for
details.  Turn on the bootstrap agent and it should work again.  You can do
so in omniNames by adding an "-ORBsupportBootstrapAgent 1" to the command
line when starting omniNames.

Kendall

                    Donnacha Forde                                                                                         
                    <dmf2k2@yahoo.com>                 To:     omniorb-list@omniorb-support.com                            
                    Sent by:                           cc:                                                                 
                    omniorb-list-admin@omniorb-s       Fax to:                                                             
                    upport.com                         Subject:     [omniORB] omniNames4 fails where omniNames3 worked     

                    01/30/2003 08:41 AM                                                                                    

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
_______________________________________________
omniORB-list mailing list
omniORB-list@omniorb-support.com
http://www.omniorb-support.com/mailman/listinfo/omniorb-list