I changed the timeout parameter in web.cfg file on my secondary server but it still not working.

Document ID : KB000053917
Last Modified Date : 14/02/2018
Show Technical Document Details

Description

I changed the Timeout parameter in web.cfg file on my primary as well as secondary servers. But it only seems to be working on the primary and not the secondary.
Are there additional files where I should change the parameter on the secondary server?

Solution

A good idea would be check the stdlog to see which file exactly is being used by the webengine on the secondary server. For example, you would messages like these in the stdlog on the secondary server:

 
 pdm_process.c    774 Process stopped (E:/PROGRA~1/CA/SERVIC~1/bin/webengine -
 q -d ANY -S web:<servername>:1 -c E:/PROGRA~1/CA/SERVIC~1/bopcfg/www/<servername>-web1.cfg return: 0
 
In this case the webengine on the server is pointing to the -web1.cfg file and hence the Timeout variable needs to set on this file for it to take effect.
Note that changes to the file need recycle of services.