[Ace-users] [tao-users] [Fwd: Re: PROBLEM-REPORT-FORM - nsdel syntax problem]

[Adam Mitz]

> -------- Original Message --------
> Subject: Re: PROBLEM-REPORT-FORM - nsdel syntax problem
> Date: Wed, 20 Feb 2008 12:56:03 -0800 (PST)
> From: jeffery.fitzgerald at gmail.com
> 
> On Feb 20, 3:57 pm, Adam Mitz <mi... at ociweb.com> wrote:
>> jeffery.fitzger... at gmail.com wrote:
>> >     ACE VERSION: 5.5.6
> 
>> >     SYNOPSIS:
>> > When i try delete a reference from my Naming Service using nsdel, I
>> > get the following error:
>>
>> > Error:
>> > (3744|3452) EXCEPTION,
>> > The following node is missing
>> > user exception, ID 'IDL:omg.org/CosNaming/NamingContext/NotFound:1.0'
>> > ID: myservice
>>
>> >     DESCRIPTION:
>> > Before I upgraded to 5.5.6, I was using 5.4a. The following syntax
>> > worked for me before the upgrade (and has actually worked since 5.2).
>>
>> > nsdel -ORBInitRef NameService=corbaloc:iiop:localhost:12345/
>> > NameService --name myservice
>>
>> > Any suggestions on what I might be doing wrong? Thanks.
>>
>> Try "--ns corbaloc:iiop:localhost:12345/NameService" instead of the
>> -ORBInitRef option.  Also, what does "nslist" report for the same arguments?
> 
> 
> Hey Adam,
> 
> That didn't seem to work for me either.  I got the following output:
> 
> nsdel --ns corbaloc:iiop:localhost:12345/NameService --name myservice
> 
> Error:
> (3404|2920) EXCEPTION, Exception in nsdel
> system exception, ID 'IDL:omg.org/CORBA/TRANSIENT:1.0'
> OMG minor code (2), described as '*unknown description*', completed =
> NO

OK, so it seems --ns is not working.  I was just trying to follow the 
documentation!

> 
> nslist is working fine for me.
> nslist -ORBInitRef NameService=corbaloc:iiop:localhost:12345/
> NameService
> Naming Service:
> ---------------
> + myservice: Object Reference
> |   Protocol: IIOP
> |   Endpoint: 192.168.200.130:12346

Going back to -ORBInitRef seems to be fine (as compared to --ns).

> 
> Would the arguments I'm passing in to the Naming Service at startup be
> of any use/have any effect?
> 

Sure, that would be good to see.  Also, add -ORBDebugLevel 10 to the 
nsdel parameters so you can see what's being sent to/from the ORB.

Thanks,
Adam Mitz
Software Engineer
Object Computing, Inc.