Can I control the network timeouts for ERPM?

Follow

Yes. There are a few different ways depending on the target system to control a timeout. These settings affect both ERPM (PWC) and RPM (RPM).

For Linux/UNIX (SSH & Telnet targets) systems there are two separate timeout values which are defined in the response.xml file used for a password change job. These are "UnmatchTimeout" and "TotalTimeout". The first value defines how long ERPM will wait for a match during any particular step of a change operation. The total timeout is the time allotted for the entire password change process.

For Windows and databases, the timeouts are controlled by default by the Windows networking stack which has a half-life of 1 minute and a total timeout of two minutes. ERPM will begin disconnecting these sessions if the following DWORD is added under registry key "HKLM\Software\[Wow6432Node\]{PWC | RPM}\ProgramOptions":

  • m_dwNetworkCallTimeoutSeconds



The default value used when this value is not present is 120 seconds. Setting this value lower may cause ERPM to disconnect from a system prematurely.

Finally, Starting with ERPM and RPM v4.80, a heartbeat monitor was included to look for jobs that are not necessarily failing but are taking an extraordinary amount of time to complete while not actually performing any work. This scenario can arise when a system that is in an indeterminate state pends a connection. The heartbeat monitor will stop the process from running (rouletteproc.exe) and and reset the status of the job. This allows ERPM and RPM to continue to process other jobs rather than pending indefinitely.

The heartbeat monitor timeout will kill the process after two minutes (120 seconds) of not receiving a heartbeat. This means a total timeout for a pending non-responsive connection will take at least two minutes. The heartbeat timeout is controlled by the following registry key under "HKLM\Software\[Wow6432Node\]{PWC | RPM}\ProgramOptions":

  • m_dwHeartbeatMonitorTimeoutOverrideSeconds



If this value is set to 0 it will use the default value of 120 seconds

Was this article helpful?
0 out of 0 found this helpful

Comments

Powered by Zendesk