Hi Duncan,<br>Thank you for your reply. <br>In this case, both Client application and Server application are running on the same machine. Since this issue occured in user's environment, we have no ORB trace log, although we're trying to get the log.<br>
We'll try to reproduce in our development environment, and feedback you while reproduced. Thanks<br>Best Regards<br>Jia Jian Ping <br><br><div class="gmail_quote">On Fri, Nov 6, 2009 at 1:33 AM, Duncan Grisby <span dir="ltr"><<a href="mailto:duncan@grisby.org">duncan@grisby.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="h5">On Thu, 2009-10-29 at 16:55 +0800, jianping jia wrote:<br>
<br>
> I use OmniORB 4.05 in my source code. Sometimes, client program<br>
> receives CORBA exception Comm_Failure_WaitForReply after some<br>
> successful calls. After that, each subsequent call only get the same<br>
> exception. Can anyone explain what error can cause that? Thanks<br>
<br>
</div></div>That means that a network connection was closed while the ORB was<br>
waiting for the reply from a call. You'll have to give us more details<br>
about the situation, including tracing from -ORBtraceLevel 25 to be able<br>
to tell you more than that.<br>
<div><div></div><div class="h5"><br>
Duncan.<br>
<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>
</div></div></blockquote></div><br>