APAR status
Closed as program error.
Error description
Client comes in with sessionID in cookie but
no valid session. Session is created, but
ID is reused because IsSessionIDInUse=true
(however, no call to DRS and there is only
one application so it can't be in use in
another webModule)
There is no gap between these lines of
trace. The invalidation thread kicks in and
invalidates the newly created session
There is no gap between these lines of trace.
The thread that created the session above
continues execution and places data into the
session object (how can this happen?? session
was invalidated. Should we not get an
illegalstateexception here?)
Client does another get session and it returns
null. New session is created. Again, sessionID
is reused because InUse=true. Again, DRS is
not called. Again, no other application that
would create session with this ID
getAttribute() returns NULL. Client was
expecting the data that was put into the session
object at [2/3/04 13:04:49:170 EST] to be there.
It is not there.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users *
****************************************************************
* PROBLEM DESCRIPTION: Session manager invalidation thread *
* incorrectly invalidates. The *
* getAttribute() method call in the *
* session object returns null. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Some of the session code is using the getLastAccessedTime()
method, which can return -1 rather 0. This causes the
invalidation thread to think it is okay to invalidate the
session.
Problem conclusion
Changed the session code so that they are using
getLastAccTime() rather than getLastAccessedTime(). With the
change, the invalidation thread correctly calculates whether it
is time to invalidate those sessions that have been inactive
for the specified period of time.
Temporary fix
Fix uploaded to
PQ99999.
Comments
APAR information |
APAR number |
PQ84502 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00S |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-02-10 |
Closed date |
2004-04-27 |
Last modified date |
2004-04-27 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|