Bug 1870 - Only first client can add a NamingContext when statically linked.
Summary: Only first client can add a NamingContext when statically linked.
Status: ASSIGNED
Alias: None
Product: TAO
Classification: Unclassified
Component: Name Service (show other bugs)
Version: 1.4.1
Hardware: All All
: P3 normal
Assignee: DOC Center Support List (internal)
URL:
Depends on:
Blocks:
 
Reported: 2004-07-09 12:28 CDT by Ossama Othman
Modified: 2004-07-19 12:49 CDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ossama Othman 2004-07-09 12:28:29 CDT
Rich Seibel from OCI reports the following:

.................................
A user supplied this patch to add the capability to add a context using
the nsadd utility.

Here are the changelog entries, first to TAO

Fri Jul  2 10:16:06 2004  Rich Seibel <seibel_r@ociweb.com>

        * utils/nslist/nsadd.cpp:
          Integrated change from Dave Knox at Intrado Inc. to add the
          ability to add a new context to the Naming Service.

        * utils/nslist/runtest.pl:
          New test added to test the ability to use the above.
.........................................

This added capability is working correctly.  However, the new test added
to verify it has exposed a problem that has been in the Naming Service for
at least back to 1.3.1 release, probably a lot further.  The problem
occurs only on static builds and is that only the first client can add a
context, subsequent clients quietly fail when trying to add contexts, but
they can add objects to existing contexts.  Further, this only occurs on
the Linux platforms, or, maybe with gcc, neither of our scoreboards show
static builds on anything but Linux and Windows.
Comment 1 Irfan Pyarali 2004-07-19 12:49:01 CDT
Accepted for tao-support.