PQ61670: VALUEUNBOUND METHOD FROM HTTPSESSIONBINDINGLISTENER IS NOT BEING CALLED UNDER THE CERTAIN CIRCUMSTANES. | |||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||
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 PQ59170Comments
APAR is sysrouted FROM one or more of the following: PQ59170 APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ61670
IBM Group: Software Group
Modified date: May 28, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.