|
| Problem | MustGather for problems with the WebSphereŽ Application Server V3.5 (all releases) Sessions and Session Management component. Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time. | | | | Solution | If you have already contacted support, continue on to the component's specific MustGather information. Otherwise, click on the following link: MustGather: Read First for all WebSphere Application Server Products.
To solve a problem with your HTTPSessions in WebSphere Application Server V3.5 (all releases), first reproduce the problem with session tracing enabled. Adding debug code to your application simplifies the task of identifying the problem. Sessions and Session Management MustGather If you can add debug code to your application prior to reproducing the problem, the following items are useful: - What sessionID encounters the problem?
- Does getSession()return null?
- Does getValue()(getAttribute)return null? If so, what were you doing a getValue()(getAttribute)on?
- If you catch an exception that is pertinent to the problem:
- Call PrintStackTrace()after catching the exception (this goes to stderr without a timestamp).
- Call System.out.println()to print out the message of the exception. This indicates that you are printing out the stack trace.
Note: If you cannot add debug code to your application prior to reproducing, please identify the sessionID that encounters the problem.Provide the following documentation:- Full XMLConfig export of the WebSphere Application Server configuration.
- Explanation of topology (number of nodes, software on each, and so forth).
- Stop WebSphere and the Web server.
- Delete everything in $WAS_HOME\logs.
- Start WebSphere.
- Bring up the WebSphere Advanced Administrative Console:
- Select your application server (for example: Default Server)
- Click the Advanced tab.
- Edit the Trace specification and Trace output file settings:
- For Trace specification, set it to the following value
Note: A colon (:) is required between the trace settings. The string must be continuous, without spaces. com.ibm.servlet.personalization.sessiontracking.*=all=enabled:com.ibm.servlet.engine.srt.*=all=enabled - For Trace output file, fill in the fully qualified filename
Trace output file example, C:\WebSphere\AppServer\logs\sessiontrace.txt
- Restart the Application Server.
- Start the Web server.
- Reproduce your problem. If you have not added debug code to your application, change your browser settings to warn before accepting cookies so that you can capture the sessionID (see link in "Related information" section below for instructions)
- Send the following files:
- Everything in $WAS_HOME\logs directory
- sessiontrace.txt
- XMLConfig export
- Follow instructions tosend diagnostic information to IBM support.
For a listing of all technotes, downloads, and educational materials specific to the Session and Sessions Management component, search the WebSphere Application Server support site for session, session management, or HTTPSession. | |
| | |
| |
|
Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Sessions and Session Management Operating system(s): Multi-Platform Software version: 3.5 Software edition: Advanced Edition, Standard Edition 3.5.x Reference #: 1053931 IBM Group: Software Group Modified date: 2004-12-08
(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.
|