You can specify additional settings for session management through setting custom properties.
To specify custom properties for session management, use the following steps:
Default clone ID length: 40
If the maximum inactive interval is less than 2 minutes, the reaper poll interval is usually between 30 to 60 seconds.
If the maximum inactive interval is more than 2 minutes and up to 15 minutes, the reaper poll interval is usually between 60 to 90 seconds.
If the maximum inactive interval is more than 15 minutes and up to 30 minutes, the reaper poll interval is usually between 120 to 180 seconds.
If the maximum inactive interval is more than 30 minutes, the reaper poll interval is usually between 240 to 300 seconds.
Because the default timeout and maximum inactive interval is 30 minutes, the reaper interval is usually between 4 and 5 minutes.
For example, you might want to use this property if you want the installation timed out sessions invalidated more frequently than 4 to 5 minutes. Specifying HttpSessionReaperPollInterval=120 ensures that sessions are invalidated within 2 minutes of timing out.
The minimum value for this property is 30 seconds. If a value less than the minimum is entered, the specified property is ignored and an appropriate value is automatically determined and used. The maximum inactive interval is the session timeout. The default is based on maximum inactive interval set in session management.
Data type | Integer |
Units | Seconds |
If HTTP session management is configured to use session persistence and the user's browser session is moving back and forth across multiple web applications you might see extra persistent store activity as the in-memory sessions for a web module are refreshed from the persistent store. As a result, the cache IDs are continually increasing and the in-memory session attributes are overwritten by those of the persistent copy.
If the configuration is a cluster, ensure that the system times of each cluster member is identical as possible.
Set the custom property to true if you are using DB2 for sessions persistence and the customSchema property is not set to the default value in the DB2 JDBC driver.
The default value is false.