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

[jeffery.fitzgerald at gmail.com]

On Feb 22, 12:53 pm, Adam Mitz <mi... at ociweb.com> wrote:
> Hi Jeff,
>
>
>
> > On Wed, Feb 20, 2008 at 6:17 PM, Adam Mitz <mi... at ociweb.com
> > <mailto:mi... 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.fitzger... at gmail.com
> >     <mailto:jeffery.fitzger... 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.- Hide quoted text -
>
> - Show quoted text -

Adam,

Just some more info to the previous problem. My application doesn't
use nsadd to add a new binding to the Naming Service; it does it
internally as an extra argument to its main() line. But I traced
through the code in nsadd and my application, and there didn't seem to
be any glaring differences (to me anyway).

Oddly enough, when I use nsadd, ndel can sucessfully remove the
binding, but my Java client application fails to start. The naming
context successfully resolves the the name, but when I try to narrow
the returned object I get a class cast exception. And of course, the
binding added to the naming context by my application can't be
removed, but narrow() in the client succeeds.

To humour myself, I replaced the current (5.5.6) nsdel.cpp with the
5.4a version and recompiled the utility. Voila, success. I guess it
may be time to upgrade my 1.2a Developer's Guide. How current is the
1.4a documentation (http://www.theaceorb.com/product/
index.html#doc1.4a)?

Thanks.

Fitz