Configuring Web Container Sessions

This section describes the HTTP session settings in the Web container. HTTP sessions are unique web sessions that have their state data written to a persistent store.

To set the session timeout value:

  1. In the tree component select the Configurations node.
  2. Select the instance you want to configure:
    1. To configure a particular instance, select the instance’s config node. For example, the default instance, server, select the server-config node.
    2. To configure the default settings for all instances, select the default-config node.
  3. Select the J2EE Containers node.
  4. Click the Session Properties tab.
  5. In the Session Timeout field enter the number of seconds that a session is valid.
  6. Click Save.

See Also:

Configuring the Manager Properties

The session manager allows you to configure how sessions are created and destroyed, where session state is stored, and the maximum number of sessions.

To change the session manager settings:

  1. In the tree component select the Configurations node.
  2. Select the instance you want to configure:
    1. To configure a particular instance, select the instance’s config node. For example, the default instance, server, select the server-config node.
    2. To configure the default settings for all instances, select the default-config node.
  3. Select the J2EE Containers node.
  4. Click the Manager Properties tab.
  5. Set the Reap Interval value.
  6. The Reap Interval field is the interval in seconds that inactive session data will be deleted from the store.

  7. Set the Max Sessions value.
  8. The Max Sessions field is the maximum number of sessions allowed.

  9. Set the Session Filename value.
  10. The Session Filename field is the file that contains the session data.

  11. Set the Session id Generator Classname value.
  12. The Session id Generator Classname field allows you to specify a custom class for generating unique session IDs. You can only use one session ID generator class per server instance, and all instances in a cluster must use the same session ID generator to prevent session key collision.

    Custom session ID generator classes must implement the com.sun.enterprise.util.uuid.UuidGenerator interface:

    package com.sun.enterprise.util.uuid;

    public interface UuidGenerator {

    public String generateUuid();

    public String generateUuid(Object obj); //obj is the session object

    }

    The class must be in the Application Server classpath.

  13. Click Save.

See Also:

Configuring the Store Properties

  1. In the tree component select the Configurations node.
  2. Select the instance you want to configure:
    1. To configure a particular instance, select the instance’s config node. For example, the default instance, server, select the server-config node.
    2. To configure the default settings for all instances, select the default-config node.
  3. Select the J2EE Containers node.
  4. Click the Store Properties tab.
  5. Set the Reap Interval.
  6. The Reap Interval field is the interval in seconds that inactive session data will be deleted from the store.

  7. Click Save.

See Also:


Legal Notices