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

[sandor.kopanyi@essnet.se]

Hi Leandro,

Thanks for the tip, but unfortunately this is not
the problem=2E 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=2E=2E=2E

Best regards,
Sandor

>-----Original Message-----
>From: MIME :leandro@hasar=2Ecom=20=
>Sent: 2001 June 28, Thursday 20:02
>To: Kop=E1nyi S=E1ndor
>Cc: omniorb-list@uk=2Eresearch=2Eatt=2Ecom
>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=20=
>forgot the omniORB=2Ecfg
>and the ORB is therefore unable to figure out where=20=
>NameService is=2E That is not
>catched by "except CORBA=2ECOMM_FAILURE"=2E
>
>Leandro Fanzone=2E
>
>sandor=2Ekopanyi@essnet=2Ese wrote:
>
>> Hi Leandro,
>>
>> Yes, I've tried it, but just suddendly "dies", without
>> any traceback=2E The only word on the screen is: Aborted=2E
>> I don't even know, what is aborted: the Python interpreter?
>> Some CORBA operation?
>>
>> If I comment out the line [obj =3D=20=
>orb=2Eresolve_initial_references("NameService")],
>> it complains about not existing object when trying to narrow -
>> but that's normal :)
>>
>> /Sandor
>>
>> >-----Original Message-----
>> >From: MIME :leandro@hasar=2Ecom >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=2Ekopanyi@essnet=2Ese wrote:
>> >
>> >> One correction: the resolve_initial_references() causes this,
>> >> not the narrowing=2E Sorry for the mistake=2E
>> >>
>> >> 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=2Eresearch=2Eatt=2Ecom'
>> >> >Subject: Abort when narrowing the naming context
>> >> >
>> >> >
>> >> >Hi,
>> >> >
>> >> >The code-snippet below aborts with a very laconic error
>> >> >message: "Aborted"=2E Nothing else=2E=2E=2E
>> >> >
>> >> >    #initialise the ORB & naming service
>> >> >    orb =3D CORBA=2EORB_init(sys=2Eargv, CORBA=2EORB_ID)
>> >> >    obj =3D orb=2Eresolve_initial_references("NameService")
>> >> >    try:
>> >> >      rootContext =3D obj=2E_narrow(CosNaming=2ENamingContext)
>> >> >    except CORBA=2ECOMM_FAILURE:
>> >> >      print "Failed to access the naming context=2E Sorry=2E=2E=2E"
>> >> >      print "(hint: is the naming service running?)"
>> >> >      sys=2Eexit(1)
>> >> >
>> >> >(The narrowing line causes this)=2E
>> >> >
>> >> >I run this on a Red Hat Linux 7=2E1 with Python 1=2E5=2E2, omniORBpy
>> >> >ver=2E 1=2E4 (behaves like this with 1=2E3 too)=2E The naming service
>> >> >is ORBacus for Java, ver=2E 4=2E0=2E5, with IBM JDK 1=2E3=2E
>> >> >
>> >> >The same stuff works fine on RedHat 6=2E2, same versions of
>> >> >Python and omniORBpy and ORBacus (on that we use Sun JDK 1=2E3)=2E
>> >> >
>> >> >Any ideeas?
>> >> >
>> >> >Best regards,
>> >> >Sandor
>> >> >
>> >
>> >
>> >
>> >
>
>
>
>