Use Cached Configuration After Update

Use this property only on recommendation from ForgeRock support, to reduce unnecessary concurrent authentication requests to AM.

When the agent receives requests after the agent config has been updated in AM, a single request thread calls AM to download the new configuration. This property manages the response for the concurrent request threads, as follows:

false: Concurrent request threads wait for the time specified by TCP Receive Timeout for the retrieving request thread to complete, and then they use the new configuration.
true: Concurrent request threads that can use the out-of-date, cached configuration do so, without waiting for the new configuration.

Set this property according to the value of Location of Agent Configuration Repository:

local: In the local bootstrap file.
central: In the AM console. The value in the AM console takes precedence over the local bootstrap file.

Default: false

Property name

com.forgerock.agents.config.use.during.update

Property aliases

com.forgerock.agents.config.use.during.update (since 4.x)

Type

Boolean: true returns true; all other strings return false.

Bootstrap property

Yes

Required property

Restart required

AM console tab

Advanced

Web Policy Agents 5.9.1

Use Cached Configuration After Update