[omniORB] Abort when resolving initial references (was: Abort when narrowing the naming context)

[Attila.Pletyak@anemo.com]

One interesting point is the name of this config file. Previously it wa=
s
/etc/omniorb.cfg, but with the new versions of omniORB it became
/etc/omniORB.cfg. It is case sensitive on Linux. Do you use it like thi=
s?

What are the contents of that file?

Sincerely,
Attila Pletyak
Anemo Ltd.
Hungary
mailto:attila.pletyak@anemo.com
http://www.anemo.com/


                                                                       =
                                                                   =20
                    sandor.kopanyi@essnet.se                           =
                                                                   =20
                    Sent by:                            To:     leandro=
@hasar.com                                                         =20
                    owner-omniorb-list@uk.resear        cc:     omniorb=
-list@uk.research.att.com                                          =20
                    ch.att.com                          Subject:     RE=
: [omniORB] Abort when resolving initial references (was: Abort    =20
                                                        when   narrowin=
g the naming context)                                              =20
                                                                       =
                                                                   =20
                    06/29/01 10:20 AM                                  =
                                                                   =20
                                                                       =
                                                                   =20
                                                                       =
                                                                   =20



Hi Leandro,

Thanks for the tip, but unfortunately this is not
the problem. I have even tried to comment out everything
in the config file, with no effect - it seems that is not
even reading the config file...

Best regards,
Sandor

>-----Original Message-----
>From: MIME :leandro@hasar.com >Sent: 2001 June 28, Thursday 20:02
>To: Kop=E1nyi S=E1ndor
>Cc: omniorb-list@uk.research.att.com
>Subject: Re: [omniORB] Abort when resolving initial references (was:
>Abort when narrowing the naming context)
>
>
>I was just thinking that perhaps when you reinstalled, you >forgot the=

omniORB.cfg
>and the ORB is therefore unable to figure out where >NameService is. T=
hat
is not
>catched by "except CORBA.COMM_FAILURE".
>
>Leandro Fanzone.
>
>sandor.kopanyi@essnet.se wrote:
>
>> Hi Leandro,
>>
>> Yes, I've tried it, but just suddendly "dies", without
>> any traceback. The only word on the screen is: Aborted.
>> I don't even know, what is aborted: the Python interpreter?
>> Some CORBA operation?
>>
>> If I comment out the line [obj =3D >orb.resolve_initial_references
("NameService")],
>> it complains about not existing object when trying to narrow -
>> but that's normal :)
>>
>> /Sandor
>>
>> >-----Original Message-----
>> >From: MIME :leandro@hasar.com >Sent: 2001 June 28, Thursday 19:44
>> >To: Kop=E1nyi S=E1ndor
>> >Subject: Re: [omniORB] Abort when resolving initial references (was=
:
>> >Abort when narrowing the naming context)
>> >
>> >
>> >Did you try catching NO_RESOURCES?
>> >
>> >Leandro Fanzone
>> >
>> >sandor.kopanyi@essnet.se wrote:
>> >
>> >> One correction: the resolve_initial_references() causes this,
>> >> not the narrowing. Sorry for the mistake.
>> >>
>> >> But the Abort is still Abort :(
>> >>
>> >> Best regrds,
>> >> Sandor
>> >>
>> >> >-----Original Message-----
>> >> >From: Kop=E1nyi S=E1ndor >Sent: 2001 June 28, Thursday 16:01
>> >> >To: 'omniorb-list@uk.research.att.com'
>> >> >Subject: Abort when narrowing the naming context
>> >> >
>> >> >
>> >> >Hi,
>> >> >
>> >> >The code-snippet below aborts with a very laconic error
>> >> >message: "Aborted". Nothing else...
>> >> >
>> >> >    #initialise the ORB & naming service
>> >> >    orb =3D CORBA.ORB_init(sys.argv, CORBA.ORB_ID)
>> >> >    obj =3D orb.resolve_initial_references("NameService")
>> >> >    try:
>> >> >      rootContext =3D obj._narrow(CosNaming.NamingContext)
>> >> >    except CORBA.COMM_FAILURE:
>> >> >      print "Failed to access the naming context. Sorry..."
>> >> >      print "(hint: is the naming service running?)"
>> >> >      sys.exit(1)
>> >> >
>> >> >(The narrowing line causes this).
>> >> >
>> >> >I run this on a Red Hat Linux 7.1 with Python 1.5.2, omniORBpy
>> >> >ver. 1.4 (behaves like this with 1.3 too). The naming service
>> >> >is ORBacus for Java, ver. 4.0.5, with IBM JDK 1.3.
>> >> >
>> >> >The same stuff works fine on RedHat 6.2, same versions of
>> >> >Python and omniORBpy and ORBacus (on that we use Sun JDK 1.3).
>> >> >
>> >> >Any ideeas?
>> >> >
>> >> >Best regards,
>> >> >Sandor
>> >> >
>> >
>> >
>> >
>> >
>
>
>
>



=