Limiting Active HTTP Sessions

An administrator can limit the number of active HTTP sessions based on the detection of a low memory condition. This is useful in avoiding out-of-memory exceptions. Once the server reaches the maximum number of active HTTP sessions, it won't accept new requests to create an HTTP session. You can configure single server instances to redirect refused requests to other servers. In a cluster, the server redirects those requests to another member of the cluster. You can configure the maximum number of HTTP sessions a Managed Server can handle by specifying the session limit in the deployment descriptor of the application, as shown here:

 <session-descriptor> <max-in-memory-sessions>12</max-in-memory-sessions> </session-descriptor> ...

Get Oracle WebLogic Server 11g Administration Handbook now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.