PQ59170: VALUEUNBOUND METHOD FROM HTTPSESSIONBINDINGLISTENER IS NOT BEING CALLED UNDER THE CERTAIN CIRCUMSTANES.

A fix is available
WebSphere Application Server Version 3.5 Fix Pack 7 (3.5.7)

APAR

APAR status
Closed as program error.

Error description
If we try to access a session object after it has been invalidat
invalidated, WebSphere will find out that the session object is
no longer valid and deletes it, but value valueUnbond method in
the session binding listener will not be called -as it should be
- although the session object will be deleted. The valueUnbound
method is called only when the session reaper finds the
invalidated session and deletes it. So, in case we try to access
a session object in the interval after it has been invalidated
and before the session reaper finds it, the session object will
be deleted without calling valueUnbound method.
Local fix
No workaround, you can use PQ54352 efix - which enables setting
of session reaper interval - and set it to minimum time of 1
second, BUT this does not neccessarily resolve the problem. The
error still remains and an efix will be provided.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server - Session       *
*                 Manager Users                                *
****************************************************************
* PROBLEM DESCRIPTION: The unbound method was not being        *
*                      called on the HttpSessionBinding        *
*                      Listener when a request for a timed     *
*                      out session was made.                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
A timedout session is invalidated by the session manager if a
request comes in for it and the invalidation thread hasn't been
able to invalidate it yet.  As part of this invalidation
processing, the unbound method was not being called on the
objects which implemented the HttpSessionBindingListener.
Problem conclusion
This fix will remove the timed out session from the cache and
let the invalidation thread call the listener as part of the
invalidation processing.
Temporary fix
PQ59170
Comments
APAR information
APAR numberPQ59170
Reported component nameWAS ADVANCED AI
Reported component ID5648C8400
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2002-03-18
Closed date2002-05-28
Last modified date2002-06-27

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:

PQ61670

Modules/Macros
SESSIONS
APAR is sysrouted TO one or more of the following:PQ61670Modules/Macros

Fix information
Fixed component nameWAS ADVANCED AI
Fixed component ID5648C8400

Applicable component levels
R350 PSYUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ59170
IBM Group: Software Group
Modified date: 2002-06-27