Managing session timeout

The Dynamic Workload Console might encounter memory leak issues in a high user count scenario if users remain connected indefinitely without logging out.

The DWC.timeout.expiration parameter in the ssl_config.xml file can be set to properly manage session timeouts. The value to assign to the parameter is not fixed, and it depends on a number of factors, like the size of the environment and the number of Dynamic Workload Console users, and might require some fine tuning.

Note: The DWC.timeout.expiration value must always be smaller than the ltpa.keys expiration value visible in the ssl_config.xml file.
Example
In the following example:
<jndiEntry jndiName="DWC.timeout.expiration" value="32400000"/>
the value of the DWC.timeout.expiration parameter is set in milliseconds, while the ltpa.keys expiration value is set in minutes:
<ltpa keysPassword="{xor}Ozo5PiozKw=="
keysFileName="${server.config.dir}/resources/security/ltpa.keys"
expiration="600"/>
<webAppSecurity ssoUseDomainFromURL="false"
logoutOnHttpSessionExpire="true"/>
<httpSession invalidationTimeout="30m"
invalidateOnUnauthorizedSessionRequestException="true" 
accessOnTimeout = "false"/>
To make the DWC.timeout.expiration parameter effective, the Java WebSphere Application Server Liberty must be restarted.