Problems creating or using HTTP sessions

Note: To view and update the Session Manager settings discussed here, use the administrative console. Select the application server that hosts the problem application, then under Additional properties , select Web Container , then Session manager. What kind of problem are you having?

• HTTP Sessions are not getting created, or are lost between requests.

• HTTP Sessions are not persistent (session data lost when application server restarts, or not shared across cluster).

• Session is shared across multiple browsers on same client machine.

• Session is not getting invalidated immediately after specified Session timeout interval.

• Unwanted sessions are being created by jsps.

• Session data intended for one client is seen by another client

• A ClassCastException error occurs during failover of a session that contains an EJB reference.

If your problem is not described here, or none of these steps fixes the problem:

• Review Troubleshooting the HTTP Session Manager for general steps on debugging Session-manager related problems.

• Review Managing HTTP sessions for information on how to configure the Session manager, and best practices for using it.

• Check to see if the problem has been identified and documented by looking at the available online support (hints and tips, technotes, and fixes).

• If you don't find your problem listed there contact IBM support.

HTTP Sessions are not getting created, or are lost between requestsBy default, the Session Manager uses cookies to store the session ID on the client between requests. Unless you intend to avoid cookie-based session tracking, ensure that cookies are flowing between WebSphere Application Server and the browser:

• Make sure the Enable cookies checkbox is checked under the Session tracking Mechanism property.

• Make sure cookies are enabled on the browser you are testing from or from which your users are accessing the application.

• Check the Cookie domain specified on the SessionManager (to view the or update the cookie settings, in the Session tracking mechanism->enable cookies property, click Modify ).

  • For example, if the cookie domain is set as ".myCom.com", resources should be accessed using that domain name, e.g. http://www.myCom.com/myapp/servlet/sessionservlet.

  • If the domain property is set, make sure it begins with a dot (.). Certain versions of Netscape do not accept cookies if domain name doesn't start with a dot. Internet Explorer honors the domain with or without a dot. For example, if the domain name is set to mycom.com, change it to .mycom.com so that both Netscape and Internet Explorer honor the cookie.

• Check the Cookie path specified on the SessionManager. Check whether the problem url is hierarchially below the Cookie path specified. If not correct the Cookie path.

• If the Cookie maximum age property is set, ensure that the client (browser) machine's date and time is the same as the server's, including the time zone. If the client and the server time difference is over the "Cookie maximum age" then every access would be a new session, since the cookie will "expire" after the access.

• If you have multiple web modules within an enterprise application that track sessions:

  • If you want to have different session settings among web modules in an enterprise application, ensure that each web module specifies a different cookie name or path, or

  • If Web modules within an enterprise application use a common cookie name and path, ensure that the HTTP session settings, such as Cookie maximum age, are the same for all Web modules. Otherwise cookie behavior will be unpredictable, and will depend upon which application creates the session. Note that this does not affect session data, which is maintained separately by Web module.

• Check the cookie flow between browser and server:

  1. On the browser, enable "cookie prompt". Hit the servlet and make sure cookie is being prompted.

  2. On the server, enable SessionManager trace. Enable tracing for the HTTP Session Manager component, by using the trace specification "com.ibm.ws.webcontainer.httpsession.*=all=enabled". After
     trace is enabled, excericise your session-using servlet or jsp, then follow the instructions for dumping and browsing the trace output .

  3. Access the session servlet from the browser.

  4. The browser will prompt for the cookie; note the jsessionid.

  5. Reload the servlet, note down the cookie if a new cookie is sent.

  6. Check the session trace and look for the session id and trace the request by the thread. Verify that the session is stable across web requests:

     • Look for getIHttpsession(...) which is start of session request.

     • Look for releaseSesson(..) which is end of servlet request.

• If you are using URL rewriting instead of cookies:

  • Ensure there are no static HTML pages on your application's navigation path.

  • Ensure that your servlets and jsp files are implementing URL rewriting correctly. For details and an example see Session tracking options.

• If you are using SSL as your session tracking mechanism:

  • Ensure that you have SSL enabled on your IBM HTTP Server or iPlanet HTTP server.

  • Review Session tracking with SSL information.

• If you are in a clustered (multiple node) environment, ensure that you have session persistence enabled.

HTTP Sessions are not persistent

If your HTTP sessions are not persistent, that is session data is lost when the
application server restarts or is not shared across the cluster:

• Check the Datasource.

• Check the SessionManager's Persistence Settings properties:

  • If you intend to take advantage of Session Persistence, verify that Persistence is set to Database .

  • Persistence could also be set to Memory to Memory Replication .

  • If you are using Database-based persistence :

    • Check the jndi name of the datasource specified correctly on SessionManager.

    • Specify correct userid and password for accessing the database.

      Note that these settings have to be checked against the properties of an existing Data Source in the admin console. The Session Manager does not automatically create a session database for you.

    • The Datasource should be non-JTA, i.e. non XA enabled.

    • Check the JVM logs for appropriate database error messages.

    • With DB2, for row sizes other than 4k make sure specified row size matches the DB2 page size. Make sure tablespace name is specified correctly.

  • If you are using memory-based persistence (available only in a network deployment environment):

    • Review .

    • Review the Internal Replication Domains properties of your Session manager.

Session is shared across multiple browsers on same client machine

This behavior is browser-dependent. It varies between browser vendors, and also may change according to whether a browser is launched as a new process or as a subprocess of an existing browser session (for example by hitting Ctl-N on Windows).

The Cookie maximum age property of the Session Manager also affects this behavior, if cookies are used as the session-tracking mechanism. If the maximum age is set to some positive value, all browser instances share the cookies, which are persisted to file on the client for the specifed maximum age time.

Session is not getting invalidated immediately after specified Session timeout interval

The SessionManager invalidation process thread runs every x seconds to invalidate any invalid sessions, where x is determined based on the Session timeout interval specified in the Session manager properties. For the default value of 30 minutes , x is around 300 seconds. In this case, it could take up to 5 minutes (300 seconds) beyond the timeout threshold of 30 minutes for a particular session to become invalidated.

Unwanted sessions are being created by jsps

As required by the JavaServer Page specification, jsps by default perform a request.getSession(true), so that a session is created if none exists for the client. To prevent jsps from creating a new session, set the session scope to false in the jsp file using the page directive as follows:

<% @page session="false" %>

Session data intended for one client is seen by another client

In rare situations, usually due to application errors, session data intended for one client might be seen by another client. This situation is referred to as session data crossover. When the DebugSessionCrossover custom property is set to true, code is enabled to detect and log instances of session data crossover. Checks are performed to verify that only the session associated with the request is accessed or referenced. Messages are logged if any discrepancies are detected. These messages provide a starting point for debugging this problem. This additional checking is only performed when running on the WebSphere-managed dispatch thread, not on any user-created threads.

For additional information on how to set this property, see article, Web container custom properties.

A ClassCastException error occurs during failover of a session that contains an EJB reference

If you run WebSphere Application Server for z/OS Version 6.0.1 and configure a session manager to replicate EJB references, a session failover might trigger display of the following exception in the server region job log:

java.lang.ClassCastException: cannot cast class        org.omg.stub.java.rmi._Remote_Stub to interface javax.ejb.EJBObject 

1. SAF is both the local operating system, as well as the user registry

2. Attribute propagation is enabled

3. An unauthenticated user initiated the session outbound request

For current information available from IBM Support on known problems and their resolution, see the IBM Support page.

For current information available from IBM Support on known problems and their resolution, see Support for WebSphere Application Server for OS/400.

IBM Support has documents that can save you time gathering information needed to resolve this problem. Before opening a PMR, see the IBM Support.

Related tasks

Troubleshooting by task

Troubleshooting by component

Searchable topic ID: rtrb_httpsessprobs