Tersus: Re: timeout

Re: timeoutDate: May 26, 2010Tags:TimeoutThere are 2 different timeout settings:

Session timeout, which applies to the ongoing session maintained between client (browser) and server (tomcat). The session is of special significance when employing authorization, as it maintains the fact that a specific user is logged-in, with his assigned permissions.
The default for this timeout is 30 minutes and is maintained by tomcat, specified in tomcat's web.xml file, as explained here.

Service timeout, which applies to each top-level service (server-side process). If a service does not return a reply within the specified time, the Tersus runtime engine, issues a timeout.
The default for this timeout is 600 seconds (10 minutes), and can be overridden for a specific server-side process, by adding the serviceTimeout property to the top-level service process initiating the server call, which can be any of the following:

A Service specified in a display/client-side context
A non-display process specified in System
A server-side Timer's Activity process

With regards to your question on the possibility of using 0/null to eliminate a service timeout, it seems that doing so will not work, and the default timeout will apply. You'll need to specify a value which is long enough to last the duration of your expected service calls.Regards,DavidSee Also:

Re: timeout

To use the full functionality of this web site, JavaScript needs to be turned on.

For best results, use the Firefox browser..

Loading ...