Discussion:
[omniORB] clientCallTimeOutPeriod and serverCallTimeOutPeriod not taking
Young An
2014-04-01 15:32:48 UTC
Permalink
Hi,

I am running tests to turn on the clientCallTimeOutPeriod and serverCallTimeOutPeriod settings. I am using omniORB 4.1.4, and I have set my settings in milliseconds.

After I brought my system down and back up again, these settings do not seem to be taking affect. In particular I was expecting to see timeout exceptions.

In my test I set the settings for clientCallTimeOutPeriod/serverCallTimeOutPeriod to 30 seconds, and in my client-side application I put in a sleep() timer in the middle of some arbitrary execution code to simulate a timeout. My sleep timer was set to 2 minutes and 30 seconds. My granularity was set to 15 seconds.

What had happened was, the entire 2:30 of sleep time was processed, and I was expecting the ORB to throw an exception at 30 seconds, per my settings.

Is there some other setting that I need to configure, or is there something fundamentally missing from my test?

Thank you

Young An
Software Developer - CMSI
(410) 953-8463 Desk
(443) 860-1153 Cell

The information contained in this email message may be privileged and/or confidential and protected from disclosure under applicable law. It is intended only for the individual to whom or entity to which it is addressed as shown at the beginning of the message. If the reader of this message is not the intended recipient, or if the employee or agent responsible for delivering the message is not an employee or agent of the intended recipient, you are hereby notified that any review, dissemination, distribution, use, or copying of this message is strictly prohibited. If you have received this message in error, please notify us immediately by return email and permanently delete this message and your reply to the extent it includes this message. Any views or opinions presented in this message or attachments are those of the author and do not necessarily represent those of the Company. All emails and attachments sent and received are subject to monitoring, reading and archival by the Company.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20140401/61b068d3/attachment.html>
Bruce Visscher
2014-04-01 17:42:15 UTC
Permalink
Young An,
?
Post by Young An
Hi,
[...]
In my test I set the settings for
clientCallTimeOutPeriod/serverCallTimeOutPeriod to 30 seconds, and in my
client-side application I put in a sleep() timer in the middle of some
arbitrary execution code to simulate a timeout. My sleep timer was set to 2
minutes and 30 seconds. My granularity was set to 15 seconds.
Perhaps I have misunderstood you but I think you would need the sleep()
call to be on the server side within the implementation of a method that
gets called from the client. Of course, the setting would be on the client
side.

HTH,
Bruce
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20140401/f54046eb/attachment.html>
Young An
2014-04-01 18:42:48 UTC
Permalink
Would I need it to be on the server side to test both the clientCallTimeOutPeriod and serverCallTimeOutPeriod settings?

I had thought that clientCallTimeOutPeriod is for the client side, and serverCallTimeOutPeriod is for the server side.

Young An
Software Developer - CMSI
(410) 953-8463 Desk
(443) 860-1153 Cell

From: Bruce Visscher [mailto:bruce.visscher at gmail.com]
Sent: Tuesday, April 01, 2014 1:42 PM
To: Young An
Cc: omniorb-list at omniorb-support.com
Subject: Re: [omniORB] clientCallTimeOutPeriod and serverCallTimeOutPeriod not taking

Young An,
[https://mailfoogae.appspot.com/t?sender=aYnJ1Y2Uudmlzc2NoZXJAZ21haWwuY29t&type=zerocontent&guid=8b214e67-4be8-4493-a951-dff8f1beba4b]?

On Tue, Apr 1, 2014 at 11:32 AM, Young An <younga at cmsinc.com<mailto:younga at cmsinc.com>> wrote:
Hi,
[...]
In my test I set the settings for clientCallTimeOutPeriod/serverCallTimeOutPeriod to 30 seconds, and in my client-side application I put in a sleep() timer in the middle of some arbitrary execution code to simulate a timeout. My sleep timer was set to 2 minutes and 30 seconds. My granularity was set to 15 seconds.

Perhaps I have misunderstood you but I think you would need the sleep() call to be on the server side within the implementation of a method that gets called from the client. Of course, the setting would be on the client side.

HTH,
Bruce
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20140401/702f1a55/attachment.html>
Young An
2014-04-07 19:39:25 UTC
Permalink
Here is additional background information regarding my issue:

A call from one of our client modules to a server module was hanging indefinitely and locking up the server module, so in order to prevent this hanging, we are trying to use omniORB?s internal settings to enforce a timeout.

Young An
Software Developer - CMSI
(410) 953-8463 Desk
(443) 860-1153 Cell

From: Young An
Sent: Tuesday, April 01, 2014 2:43 PM
To: 'Bruce Visscher'
Cc: omniorb-list at omniorb-support.com
Subject: RE: [omniORB] clientCallTimeOutPeriod and serverCallTimeOutPeriod not taking

Would I need it to be on the server side to test both the clientCallTimeOutPeriod and serverCallTimeOutPeriod settings?

I had thought that clientCallTimeOutPeriod is for the client side, and serverCallTimeOutPeriod is for the server side.

Young An
Software Developer - CMSI
(410) 953-8463 Desk
(443) 860-1153 Cell

From: Bruce Visscher [mailto:bruce.visscher at gmail.com]
Sent: Tuesday, April 01, 2014 1:42 PM
To: Young An
Cc: omniorb-list at omniorb-support.com<mailto:omniorb-list at omniorb-support.com>
Subject: Re: [omniORB] clientCallTimeOutPeriod and serverCallTimeOutPeriod not taking

Young An,
[https://mailfoogae.appspot.com/t?sender=aYnJ1Y2Uudmlzc2NoZXJAZ21haWwuY29t&type=zerocontent&guid=8b214e67-4be8-4493-a951-dff8f1beba4b]?

On Tue, Apr 1, 2014 at 11:32 AM, Young An <younga at cmsinc.com<mailto:younga at cmsinc.com>> wrote:
Hi,
[...]
In my test I set the settings for clientCallTimeOutPeriod/serverCallTimeOutPeriod to 30 seconds, and in my client-side application I put in a sleep() timer in the middle of some arbitrary execution code to simulate a timeout. My sleep timer was set to 2 minutes and 30 seconds. My granularity was set to 15 seconds.

Perhaps I have misunderstood you but I think you would need the sleep() call to be on the server side within the implementation of a method that gets called from the client. Of course, the setting would be on the client side.

HTH,
Bruce
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20140407/cd098066/attachment.html>
Loading...