Re: client blocked
YDC関谷正明 via omniORB-list <[email protected]> Fri, 15 Sep 2023 14:11:59 +0900
| Newsgroups | gmane.comp.corba.omniorb.user |
|---|---|
| Message-ID | <CAECkHYqaCdv5TcrggHYeqpSZk_WyBwiDrumG=oibvc5R3cC9rg@mail.gmail.com> |
--===============0919072641736510623== Content-Type: multipart/alternative; boundary="0000000000009adf6c06055ed5fd" --0000000000009adf6c06055ed5fd Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Duncan. Thank you for the comment. It's difficult to reproduce this situation. This system has worked for over 20 years. But I haven't seen this situation. Regards. 2023=E5=B9=B49=E6=9C=8813=E6=97=A5(=E6=B0=B4) 4:51 Duncan Grisby <duncan@gr= isby.org>: > On Wed, 2023-09-06 at 18:37 +0900, YDC=E9=96=A2=E8=B0=B7=E6=AD=A3=E6=98= =8E via omniORB-list wrote: > > > > I'm using omniORB4.2.3 for a long time. It works very fine. > > However recently I encountered an issue where the client was blocking > > while waiting for the server's response. > > omniORB 4.2.3 is very old now =E2=80=93 nearly five years old. There are = quite > a few bug fixes in the 4.2.x line since then. > > [...] > > I have two questions. > > 1. What is the client waiting for ? > > 2. The client is launched with "-ORBclientCallTimeOutPeriod" option, > > but it doesn't seem to be effective. Is the option not working? > > There is no obvious reason for it to be blocked. Can you reproduce the > situation with -ORBtraceLevel 25 -ORBtraceInvocations 1 ? > > Duncan. > > -- > Duncan Grisby <[email protected]> > --0000000000009adf6c06055ed5fd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>Hi Duncan.</div><div>Thank you for the comment.</div>= <div>It's difficult to reproduce this situation. This system has worked= for over 20 years.<br>But I haven't seen this situation.</div><div><br= ></div><div>Regards.</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" c= lass=3D"gmail_attr">2023=E5=B9=B49=E6=9C=8813=E6=97=A5(=E6=B0=B4) 4:51 Dunc= an Grisby <<a href=3D"mailto:[email protected]">[email protected]</a>>= ;:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0= .8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Wed, 2023-= 09-06 at 18:37 +0900, YDC=E9=96=A2=E8=B0=B7=E6=AD=A3=E6=98=8E via omniORB-l= ist wrote:<br> <br> <br> > I'm using omniORB4.2.3 for a long time. It works very fine.<br> > However recently I encountered an issue where the client was blocking<= br> > while waiting for the server's response. <br> <br> omniORB 4.2.3 is very old now =E2=80=93 nearly five years old. There are qu= ite<br> a few bug fixes in the 4.2.x line since then.<br> <br> [...]<br> > I have two questions.<br> > 1. What is the client waiting for ?<br> > 2. The client is launched with "-ORBclientCallTimeOutPeriod"= option, <br> > =C2=A0 =C2=A0but it doesn't seem to be effective. Is the option no= t working?<br> <br> There is no obvious reason for it to be blocked. Can you reproduce the<br> situation with -ORBtraceLevel 25 -ORBtraceInvocations 1=C2=A0 =C2=A0?<br> <br> Duncan.<br> <br> -- <br> Duncan Grisby <<a href=3D"mailto:[email protected]" target=3D"_blank">du= [email protected]</a>><br> </blockquote></div><div><br></div></div> --0000000000009adf6c06055ed5fd-- --===============0919072641736510623== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ omniORB-list mailing list [email protected] https://www.omniorb-support.com/mailman/listinfo/omniorb-list --===============0919072641736510623==--