HTTP session manager troubleshooting tips

Use troubleshooting tips for problems creating or using HTTP sessions with your web application hosted by WebSphere® Application Server.

Here are some steps to take:
  • [AIX Solaris HP-UX Linux Windows]See the HTTP session problems information to see if your specific problem is described.
  • [AIX Solaris HP-UX Linux Windows]View the JVM logs for the application server which hosts the problem application:
    1. Look at the messages that are written while each application is starting. Specifically, see the messages that are written between the following two messages:
      Starting application: application
      Application started: application
    2. Within this block, look for any errors or exceptions containing a package name of If no errors are found, this result indicates that the session manager started successfully.
    3. The error message, SRVE0054E: An error occurred while loading session context and web application, indicates that SessionManager did not start properly for a given application.
    4. Look within the logs for any messages that are related to the Session Manager. These messages are in the format SESNxxxxE for error messages and SESNxxxxW for warning messages, and xxxx specifies the number for the error. Look up the extended error definitions in the Session Manager message table.
  • See Best practices for using HTTP Sessions.

  • [AIX Solaris HP-UX Linux Windows]To dynamically view the number of sessions as a web application is running, enable performance monitoring for HTTP sessions. Monitoring performance provides information to help you determine if sessions are actually being created.
  • [AIX Solaris HP-UX Linux Windows]To learn how to view the HTTP session counters as the application runs, see Monitoring performance with Tivoli® Performance Viewer (formerly Resource Analyzer).
  • Alternatively, a special servlet can be invoked that displays the current configuration and statistics related to session tracking. [AIX Solaris HP-UX Linux Windows]This servlet has all the counters that are in performance monitor tool and has some additional counters.
    • Servlet name:
    • You can invoke this servlet from any web module that is enabled to serve by class name. For example, using default_app, http://localhost:9080/servlet/
      To enable serve by class name feature, set the web container custom property to false, as shown in the following example:

      For more information, see

    • If you are viewing the module using the serve by class name feature, be aware that this module might be viewable by anyone who can view the application. You can map a specific, secured URL to the servlet instead and disable the serve servlets by classname setting.
  • [AIX Solaris HP-UX Linux Windows]Enable tracing for the HTTP Session Manager component.
    The following trace can help diagnose problems:
    • If you do not use any persistence:*=all:*=all
    • If you use database persistence:*=all:*=all:
    • If you use memory-to-memory persistence:*=all:*=all:*=all
    See the MustGather sessions and session management problems in WebSphere Application Server information to learn more about collecting required data for sessions and session management problems.
  • If you are using database-based persistent sessions, look for problems related to the data source the Session Manager relies on to keep session state information. For details on diagnosing database related problems see Errors accessing a datasource or connection pool

Error message SRVE0079E Servlet host not found after you define a port

Error message SRVE0079E can occur after you define the port in WebContainer > HTTP Transports for a server, indicating that you do not have the port defined in your virtual host definitions. To define the port,
  1. On the administrative console, go to Environment > Virtual Hosts > default_host> Host Aliases> New
  2. Define the new port on host "*"

The application server gets EC3 - 04130007 ABENDs

To prevent an EC3 - 04130007 abend from occurring on the application server, change the HTTP Output timeout value. The custom property ConnectionResponseTimeout specifies the maximum number of seconds the HTTP port for an individual server can wait when trying to read or write data. For instructions on how to set ConnectionResponseTimeout, see the topic HTTP transport channel custom properties.

If these steps do not address your problem, 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 do not find your problem referenced on this site, contact IBM support.

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

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