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

[Adam Mitz]

Hi Jeff,
> On Wed, Feb 20, 2008 at 6:17 PM, Adam Mitz <mitza at ociweb.com 
> <mailto:mitza at ociweb.com>> wrote:
>
>     > -------- 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
>     <mailto:jeffery.fitzgerald at gmail.com>
>     >
>     > On Feb 20, 3:57 pm, Adam Mitz <mi... at ociweb.com
>     <mailto:mi... at ociweb.com>> wrote:
>     >> jeffery.fitzger... at gmail.com
>     <mailto: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
>     <http://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
>     <http://omg.org/CORBA/TRANSIENT:1.0>'
>     > OMG minor code (2), described as '*unknown description*',
>     completed =
>     > NO
>
I was able to replicate this when the bound IOR itself was not 
reachable.  Is this the case in your scenario?
 From a quick code inspection, nsdel is using resolve to get back the 
IOR, then attempting to narrow it to a naming context.  This should 
probably be surrounded by try/catch to prevent this error.  An 
alternative would be to use list(), but that could be inefficient when 
there are lots of bindings.  You're welcome to submit a patch for this, 
or sponsor your commercial support company of choice (of course I 
recommend OCI) to fix it for you.

Thanks,
Adam Mitz
Software Engineer
Object Computing, Inc.