[omniORB] clientCallTimeOutPeriod and serverCallTimeOutPeriod not taking

[Young An]

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>