Consequence to enlarge timeout setting

[Former Member]

To get our Webdynpro application not getting timed-out, we like to set the setting exparationTime to a bigger number then the default timeout setting of the server. What's then the consequence of enlarging? Is this only affecting security or are there any other negative results?

Thank you.

[asif_hirani]

Hi ,

Timeout setting is not Application specific..which means when you increase server timeout setting (normally 60sec) more than default it applies to all the applications running on that server..

you may not be knowing what all application will be running on your server in future and more important how many parallel instants of those application will keep waiting for execution as server time-out was increased.leading to JAM on those server nodes and other user's not being able to grab the session and getting dispatcher / server node unavaialble error.

and if user's simply click close window button after click execute Function from backend- which takes longer time server still keeps session active on nodes until application was timed.

this setting will apply not only to custom application but also standard application and services running on your server..

I don't think it's best way to increase time-out parameter for your server instead you should fine-tune/optimize application which takes so long to execute..

Regards

Asif