<div>Thanks, Duncan. I have gotten the details via tracing. One lock is used to serialize the access to gethostbyname. And when some host resolution becomes slow, other accesses will be blocked. So the immediate workaround may be to faciliate the host name resolution via configuring all hosts in the host file.</div>
<div>Best Regards <br>Jia Jian Ping<br></div>
<div class="gmail_quote">On Wed, May 5, 2010 at 12:10 AM, Duncan Grisby <span dir="ltr"><<a href="mailto:duncan@grisby.org">duncan@grisby.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div></div>
<div class="h5">On Thu, 2010-04-29 at 22:54 +0800, jianping jia wrote:<br><br>> I use multiple threads to access server server applications via CORBA<br>> calls. After several normal connections, the fsebsequent CORBA calls<br>
> will be slower and slower. From omniorb log, the slowness was caused<br>> by client wait for connection established. Appreciate if you can<br>> provide any clue to troubleshoot it. Many thanks<br><br></div></div>
It would help if you could send the logs that show what you are<br>seeing...<br><br>Duncan.<br><font color="#888888"><br>--<br> -- Duncan Grisby --<br> -- <a href="mailto:duncan@grisby.org">duncan@grisby.org</a> --<br>
-- <a href="http://www.grisby.org/" target="_blank">http://www.grisby.org</a> --<br><br><br></font></blockquote></div><br>