PQ66485: RUNTIMEEXCEPTION THROWN FROM VALUEUNBOUND() CAUSES THE SESSION MANAGER INVALIDAITON THREAD TO DIE

Fixes are available
WebSphere Application Server Version 3.5 Fix Pack 7 (3.5.7)
WebSphere Application Server Version 4.0 Fix Pack 5 (Version 4.0.5)
PQ66485, 3.5.6: Session Invalidation thread is killed if a Runtime Exception is

APAR

APAR status
Closed as program error.

Error description
Customer is putting an object A that implements the
HTTPSessionBindingListener interface into the HTTPSession. The
invalidation thread runs and attempts to invalidate an inactive
HTTPSession that contains this object. When the valueUnbound()
is called on object A, it throws a RuntimeException. This
results in the invalidation thread being terminated.
Local fix
catch the RuntimeException in the valueUnbound() method
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server -- Session      *
*                 Manager Users                                *
****************************************************************
* PROBLEM DESCRIPTION: Session Invalidation thread is killed   *
*                      if a Runtime Exception is thrown from   *
*                      the valueUnbound() method of an object  *
*                      bound to the HttpSession object.        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The Session Invalidation Thread wakes up every 3- 5 minutes
based on the configuration and invalidates all the timed out
sessions.  As part of Session Invalidation, the valueUnbound()
method of the HttpSessionBindingListener is called.  If a
RuntimeException gets thrown in the valueUnbound() method, the
invalidation thread should catch the exception and stop that
run of the thread.  Instead, the Session Manager was abruptly
terminating when a Runtime Exception was thrown from the
valueUnbound() method.
Problem conclusion
This fix will cause the Runtime Exception to be caught and the
invalidation thread execution to resume after one sleep
interval.
Temporary fix
PQ66485.jar
Comments
APAR information
APAR numberPQ66485
Reported component nameWAS ADVANCED AI
Reported component ID5648C8400
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2002-09-23
Closed date2002-11-11
Last modified date2002-11-12

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:

PQ68150

Modules/Macros
SESSIONS
APAR is sysrouted TO one or more of the following:PQ68150Modules/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 #: PQ66485
IBM Group: Software Group
Modified date: 2002-11-12