[Ace-users] [tao-users] How to set the NS multicast discovery timeout
Hans Utz
hans.utz at nasa.gov
Mon Feb 4 18:33:51 CST 2008
Hi Keith,
I don't think there is an option for that. - So you can hunt down the
timeout in the code base and recompile. But I'd suggest another route:
- Make the NS start with always the same IOR (specifying a port
with the ORBEndpoint option is all it takes).
- Use the NameServiceIOR environment variable to point to locate the NS.
(As the NS IOR does not change, you can put it in .bashrc etc.)
- Use specify the relative round trip timeout QoS for the NS-IOR,
before using it.
It's standard, will work with any ORB and will also give you an
exception, if the network hangs somewhen later.
Cheers,
Hans
Keith Nicewarner wrote:
> When using the multicast discovery feature for the naming service, a
> client will wait 10 sec before giving up if the NS isn't found. We'd
> like the client to fail quicker (say, after waiting for 1 sec). Is
> there a command-line option to specify the discovery timeout?
>
> Thanks,
> Keith.
>
>
> ********************************************************
>
> Dr. Keith Nicewarner keith.nicewarner at spacedev.com
> <mailto:keith.nicewarner at spacedev.com>
>
> Chief Software Architect 858-375-2079
>
> SpaceDev, Inc. www.spacedev.com
> <http://www.spacedev.com/>
>
> 13855 Stowe Drive San Diego, CA, 92064
>
> ********************************************************
>
> /This email message and any information or files contained within or
> attached to this message may be privileged, confidential, proprietary
> and protected from disclosure and is intended only for the person or
> entity to which it is addressed. This email is considered a business
> record and is therefore property of the SpaceDev, Inc. Any direct or
> indirect review, re-transmission, dissemination, forwarding, printing,
> use, disclosure, or copying of this message or any part thereof or other
> use of or any file attached to this message, or taking of any action in
> reliance upon this information by persons or entities other than the
> intended recipient is prohibited. If you received this message in
> error, please immediately inform the sender by reply e-mail and delete
> the message and any attachments and all copies of it from your system
> and destroy any hard copies of it. No confidentiality or privilege is
> waived or lost by any mis-transmission. SpaceDev, Inc. is neither
> liable for proper, complete transmission or the information contained in
> this communication, nor any delay in its receipt or any virus contained
> therein. No representation, warranty or undertaking (express or
> implied) is given and no responsibility or liability is accepted by
> SpaceDev, Inc., as to the accuracy or the information contained herein
> or for any loss or damage (be it direct, indirect, special or other
> consequential) arising from reliance on it.// //NOTICE: The information
> contained in this transmission may contain technical data controlled for
> export by the U.S. Department of State, under the International Traffic
> in Arms Regulations (ITARs). Disclosure (including oral or visual
> disclosure) or transfer of this information to foreign persons is
> prohibited without U.S. Government authorization.///
>
>
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> tao-users mailing list
> tao-users at mail.cse.wustl.edu
> http://mail.cse.wustl.edu/mailman/listinfo/tao-users
More information about the Ace-users
mailing list