APAR status
Closed as program error.
Error description
Objects that implement javax.servlet.http.HttpSessionListener
sometimes do not get the listener processed in clustered env.
If the session object was created in one JVM but invalidated
in another JVM by the invalidation thread, the listener is
not processed properly.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: A new interface and callback funciton is *
* introduced: *
* javax.servlet.http.HttpSession.Listener:: *
* sessionRemoveFromCache() *
* *
* This method is called when the session is *
* removed from cache. *
****************************************************************
* PROBLEM DESCRIPTION: New interface required: *
* javax.servlet.http.HttpSession.Listener *
****************************************************************
* RECOMMENDATION: *
****************************************************************
If a user has his/her own way of keeping track of the session
data per JVM, and if the session data is invalidated in a
different JVM, say JVM2, compared to the one that the session
data was created, say JVM1; there can be memory leak problem
in JVM 1.
The workaround/fix is to have customer's application to
implement IBMSessionListener interface, that the listener
will be called when the session is removed from cache.
Introducing IBMSessionListener is a possible solution because
the removeFromCache() method is called on all JVMs.
Problem conclusion
The problem is now resolved by adding a new kind of
Listener--IBMSessionListener. Listener that implements
IBMSessionListener will be called when the session data is
removed from cache.
Temporary fix
Fix uploaded to
PQ99999.
Comments
APAR information |
APAR number |
PQ81248 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00A |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2003-11-21 |
Closed date |
2004-01-20 |
Last modified date |
2004-01-20 |
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 |
|