PQ63816, 3.5.6: Session object are being cached upon creation
Downloadable files
Abstract
In persistent mode on a session create the session is not being persisted to the
database till the service method ends.
Download Description
PQ63816 resolves the following problem:
USERS AFFECTED:
WebSphereŽ Application Server -- SessionManager Users
PROBLEM DESCRIPTION:
In persistent mode on a session create the session is not being persisted to the database until the service method ends.
The symptons of the problem are that the session object is returned as a null value on the second request for it. This fix will not be helpful if the session object is being returned as null other than the second request. With session persistence enabled, a session object gets created on the first request for it. If another request comes for the same session object before the session manager has been able to persist the object and the request goes to another clone, the session manager will return a null value because the session object hasn't been persisted yet and been put within the cache of the first clone. This behavior can be seen sometimes even if the second request goes to the same clone as the first request did since the session manager puts the session object into the cache only at the end of the
service method.
PROBLEM CONCLUSION:
This fix supersedes PQ59155 which was opened originally for this problem but uncovered some other bug in the base version of the code.
Prerequisites
None
Installation instructions
Please refer to the readme for detailed installation instructions