If you have already contacted support, continue on to the
Session and Session Management component specific MustGather information.
Otherwise, click on the following link: MustGather:
Read First for all WebSphere Application Server Products.
The first step in solving a problem with your HTTPSessions in WebSphere
Application Server V4.0 (all releases) is to reproduce the problem with
session tracing enabled. Adding debug code to the application simplifies
the task of identifying the problem.
Attention: Prior to V4.0.6, session trace does not start until the
session manager invalidation thread has run once. Wait 5 minutes after the
application server has started before attempting to recreate.
Sessions and Session Management MustGather
If you can add debug code to your application prior to reproducing the
problem, the following information is 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 also indicates that you are printing out the stack
trace.
Note: If you cannot add debug code to your application prior to
reproducing, 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 install_root\logs.
- Start WebSphere.
- Bring up the WebSphere Application Server Advanced administrative
console and select yourAapplication Server (for example: Default
Server).
- Click on the Services tab. Select Trace service, then
click Edit properties.
- For Trace:
- Set it to the following value:
com.ibm.servlet.personalization.sessiontracking.*=all=enabled:com.ibm.servlet.engine.srt.*=all=enabled
- Note: A colon (:) is required between the trace settings.
The string must be continuous, without spaces.
- For Trace output file:
- Click Specify.
- Type the fully-qualified filename; for example:
C:\WebSphere\AppServer\logs\sessiontrace.txt
- Click OK, then click Apply.
- Restart the application server.
- Wait 5 minutes.
- If the problem might occur in the Session Affinity component (for
example, the request is being bounced from clone to clone), enable plugin
tracing by changing the LogLevel to Trace in the plugin-cfg.xml on the Web
server:
<Log LogLevel="Trace"
Name="D:/WebSphere/AppServer/logs/native.log"/>
- Start the Web server.
- Reproduce your problem. If you did not add 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 install_root\logs
directory
- sessiontrace.txt
- XMLConfig export
- sessionID that encounters the problem
- native.log from Web server systems (from step 13)
- Follow instructions to send
diagnostic information to IBM support.
For a listing of all Technotes, Downloads, and educational materials
specific to the Session and Session Management component, search the WebSphere
Application Server support site for session, session management, or
HTTPSession. |