Session management settings
Use this page to manage HTTP session support. This support includes specifying a session tracking mechanism, setting maximum in-memory session count, controlling overflow, and configuring session timeout.
To view this administrative console page at the web container level, click
.Session tracking mechanism
Mechanism | Function | Default |
---|---|---|
Enable SSL ID tracking | Specifies
that session tracking uses Secure Sockets Layer (SSL) information as a session ID. Enabling SSL
tracking takes precedence over cookie-based session tracking and URL rewriting.
There are two parameters available if you enable SSL ID tracking: SSLV3Timeout and Secure Authentication Service (SAS). SSLV3Timeout specifies the time interval after which SSL sessions are renegotiated. This parameter is a high setting and modification does not provide any significant impact on performance. The SAS parameter establishes an SSL connection only if it goes out of the Java™ Virtual Machine (JVM) to another JVM. If all the beans are co-located within the same JVM, the SSL used by SAS does not hinder performance. These parameters are set by editing the sas.server.properties and sas.client.props files, located in the product_installation_root/properties directory, where product_installation_root is the directory where WebSphere® Application Server is installed. Important: SAS is supported only between Version 6.0.x and previous version servers that have been federated in a Version 6.1 cell.
|
false (cleared) |
Enable cookies | Specifies that session tracking uses cookies to carry session IDs. If cookies
are enabled, session tracking recognizes session IDs that arrive as cookies and tries to use cookies
for sending session IDs. If cookies are not enabled, session tracking uses Uniform Resource
Identifier (URL) rewriting instead of cookies (if URL rewriting is enabled). Enabling cookies takes precedence over URL rewriting. Click Enable cookies to change these settings. Application level session management settings override the server level session management settings. Because session management is defined at the application level, enabling cookies for the administration console is handled in the deployment.xml file. Cookie names in the web.xml file override application level and server level session management settings. Further, cookie names from a ServletContextListener object override all settings. |
true (selected) |
Enable URL rewriting | Specifies that the session management facility uses rewritten URLs to carry the session IDs. If URL rewriting is enabled, the session management facility recognizes session IDs that arrive in the URL if the encodeURL method is called in the servlet. | false (cleared) |
Enable protocol switch rewriting | This option is only available when Enable URL rewriting is selected. This option specifies that the session ID is added to a URL when the URL requires a switch from HTTP to HTTPS or from HTTPS to HTTP. If rewriting is enabled, the session ID is required to go between HTTP and HTTPS. | false (cleared) |
Maximum in-memory session count
Specifies the maximum number of sessions to maintain in memory for each web module.
Allow overflow
Specifies that the number of sessions in memory can exceed the value specified by the Max in-memory session count property. This option is valid only in non-distributed sessions mode.
Session timeout
Specifies how long a session can go unused before it is no longer valid. Specify either Set timeout or No timeout. Specify the value in minutes greater than or equal to two.
The value specified in a web module deployment descriptor file takes precedence over the administrative console settings. However, the value of this setting is used as a default when the session timeout is not specified in a web module deployment descriptor. To preserve performance, the invalidation timer is not accurate to the second. When the write frequency is time-based, ensure that this value is least twice as large as the write interval.
Security integration
Specifies that when security integration is enabled, the session management facility associates the identity of users with their HTTP sessions. Session security (security integration) is enabled by default.
Serialize session access
Specifies that concurrent session access in a given server is not permitted.
Mechanism | Function |
---|---|
Maximum wait time | Specifies the maximum amount of time a servlet request waits on an HTTP session before starting. This parameter is optional and expressed in seconds. The default is five seconds. Under normal conditions, a servlet request waits for access to an HTTP session and is notified by the request that currently owns the given HTTP session when the request finishes. |
Allow access on timeout | Specifies whether the servlet starts normally or stops processing from a timeout. The servlet starts normally when this box is checked. If this box is not checked, the servlet stops processing and error logs are generated. |