TAO naming service

最新推荐文章于 2020-12-23 21:17:59 发布

masterz

最新推荐文章于 2020-12-23 21:17:59 发布

阅读量1.7k

点赞数

CC 4.0 BY-SA版权

分类专栏： Linux CORBA TAO 文章标签： service object network ubuntu performance library

本文链接：https://blog.youkuaiyun.com/masterz/article/details/6963764

Linux CORBA TAO 专栏收录该内容

1 篇文章

订阅专栏

本文探讨了在不同网络环境下使用两种方法启动CORBA NameService时的表现差异，一种是指定端口的方法，另一种是让NameService自行选择端口。在公共Wi-Fi环境中观察到了10秒左右的操作延迟，并分析了可能的原因。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

My environment: ACE TAO 6.0.5, Ubuntu 11.10 64bit, g++ (Ubuntu/Linaro 4.6.1-9ubuntu3)

There are two different ways to start NameService:

tao_cosnaming -ORBEndPointiiop://127.0.0.1:12345

tao_cosnaming -m 1

The first method specifies the port used by NameService, the second method let NameService find some port to use. Note: it will use different port if you restart tao_cosnaming by second method. The following command will report which port is used by tao_cosnaming:

onega@6930p:~$ lsof | grep LISTEN | grep tao_cos
tao_cosna 2789 onega 5u IPv4 29955 0t0 TCP *:47749 (LISTEN)

for the multicast mode, I also observed 10 seconds wait time for some operation:

onega@6930p:~$ tao_cosnaming -m 1

onega@6930p:~$workspace/echoserver/Debug/echoserver

workspace/echoserver/Debug/echoserverbefore ORB_init 15:8:52.278679

after ORB_init 15:8:52.283312

after resolve RootPOA 15:9:2.318345 // about 10 seconds wait time in a large wireless network (free public wifi of a library).

after narrow POA 15:9:2.318409

Echo_i

after create sevant object 15:9:2.318445

after activate sevant object 15:9:2.318522

IOR:010000001700000049444c3a436f726261546573742f4563686f3a312e30000001000000000000006c000000010102000c00000036393330702e6c6f63616c00b39800001b00000014010f005253548e1bbe4ef9da04000000000001000000010000000002000000000000000800000001000000004f41540100000018000000010000000100010001000000010001050901010000000000/nbindObjectToNamebind successfully - Echo

after bind sevant object 15:9:2.448694

after activate POAManager 15:9:2.448764

But I didn't observe any delay at home (private wifi network).

onega@6930p:~$ workspace/echoserver/Debug/echoserver
workspace/echoserver/Debug/echoserver before ORB_init 22:19:54.5681
after ORB_init 22:19:54.7164
after resolve RootPOA 22:19:54.12636
after narrow POA 22:19:54.12671
Echo_i
after create sevant object 22:19:54.12690
after activate sevant object 22:19:54.12729
IOR:010000001700000049444c3a436f726261546573742f4563686f3a312e300000010000000000000070000000010102001100000036393330702e7a74652e636f6d2e636e0000b1dd1b00000014010f005253548a80be4e163100000000000001000000010000000002000000000000000800000001000000004f41540100000018000000010000000100010001000000010001050901010000000000/nbindObjectToName bind successfully - Echo
after bind sevant object 22:19:54.24699
after activate POAManager 22:19:54.24732

for first method, the performance of CORBA is not stable in the public wifi environment. Sometimes it is quite fast, sometimes I observed 5 seconds delay.

workspace/echoclient/Debug/echoclient-o NamingService -ORBInitRefNameService=corbaloc:iiop:127.0.0.1:12345/NameService

onega@6930p:~$workspace/echoclient/Debug/echoclient -ORBInitRefNameService=corbaloc:iiop:127.0.0.1:12345/NameService

Usage:workspace/echoclient/Debug/echoclient Now: Sat Nov 12 15:59:52 2011

BeforeORB_init 15:59:52.335153

AfterORB_init 15:59:52.339106

Afterresolve NameService 15:59:52.339315

mainconnected to NameService 15:59:52.341434

Afterresolve Echo 15:59:52.341994

AfterCorbaTest::Echo::_narrow 15:59:52.342054

Request:[Hello!], Response: [Hello!] 15:59:52.342066

Request:[Hello!], Response: [Hello!] 15:59:57.493363

Request:[Hello!], Response: [Hello!] 15:59:57.493753