Techniques for HTTPSession debugging in WebSphere Application Server
To dynamically view the number of sessions as a Web application is running, enable performance monitoring for HTTP sessions. This will give you an indication as to whether sessions are actually being created.
Alternatively, a special servlet can be invoked that displays the current configuration and statistics related to session tracking. This servlet has all the counters that are in performance monitor tool and has some additional counters.
To dynamically view the number of sessions as a Web application is running, enable performance monitoring for HTTP sessions. This will give you an indication as to whether sessions are actually being created.
Alternatively, a special servlet can be invoked that displays the current configuration and statistics related to session tracking. This servlet has all the counters that are in performance monitor tool and has some additional counters.
- Servlet name: com.ibm.ws.webcontainer.httpsession.IBMTrackerDebug.
- It can be invoked from any Web module which is enabled to serve
by class name. For example, using default_app, http://localhost:9080/servlet/com.ibm.ws.webcontainer.httpsession.IBMTrackerDebug.Note: If you have enabled the serve-by-class-name feature and want to disable the IBMTrackerDebug servlet, then specify the web container custom property, com.ibm.ws.webcontainer.donotservebyclassname.See Web container custom properties for more information on how to set this property.
- If you are viewing the module via the serve-by-class-name feature, be aware that it may be viewable by anyone who can view the application. You may wish to map a specific, secured URL to the servlet instead and disable the serve-servlets-by-classname feature.
