Orbix NS object (?) listing... - Object

Hi Graham,

The Orbix "itadmin ns list" command prior to the 6.0 release would in
certain circumstances check to see if a node in the NamingService graph
was a NamingContext by narrowing. If the _narrow() needed to go
remote, and in the course of the call received an exception (TRANSIENT,
etc), the command wasn't able to contact the server to confirm the
type. However, the node was most likely an Object in a
currently-inactive server, and so the command output "Object(?)" as
you're observing. If the command could definitively deduce that the
Object wasn't of type NamingContext, it would output "Object" without
the question mark.

While this method was fine for smaller naming graphs, some Orbix Naming
Service deployments have huge graphs, and contacting the servers was
slow and error-prone. To speed things up for these customers, we
changed the way the "itadmin ns list" command works for release 6.0 and
higher to not require that remote _narrow() call. So, from version 6.0
onwards, things are a lot faster, and you won't see the "(?)" being
output.

Regards,
Conor
IONA Technologies

Hi Conor,

thanks a million for that. That response is *precisely* what I was
looking for.
The (?) was indeed present because the server was unavailable and when
the server is "up" the (?) is no longer present. You're absolutley
correct.


thanks for the info, helped a treat.

Cheers

Graham


"Conor" <jjames.flynn@gmail.com> wrote in message news:<1107446041.276409.68140@f14g2000cwb.googlegroups.com>...
> Hi Graham,
>
> The Orbix "itadmin ns list" command prior to the 6.0 release would in
> certain circumstances check to see if a node in the NamingService graph
> was a NamingContext by narrowing. If the _narrow() needed to go
> remote, and in the course of the call received an exception (TRANSIENT,
> etc), the command wasn't able to contact the server to confirm the
> type. However, the node was most likely an Object in a
> currently-inactive server, and so the command output "Object(?)" as
> you're observing. If the command could definitively deduce that the
> Object wasn't of type NamingContext, it would output "Object" without
> the question mark.
>
> While this method was fine for smaller naming graphs, some Orbix Naming
> Service deployments have huge graphs, and contacting the servers was
> slow and error-prone. To speed things up for these customers, we
> changed the way the "itadmin ns list" command works for release 6.0 and
> higher to not require that remote _narrow() call. So, from version 6.0
> onwards, things are a lot faster, and you won't see the "(?)" being
> output.
>
> Regards,
> Conor
> IONA Technologies