APAR status |
Closed as program error.
| Error description
Env: WAS 3.5.4. on Sun Solaris, 3 clones with session affinity
enabled. The affinity seems to be handled after a few requests
but not as designed. The affinity is only established after the
second visit but more visits are often needed.
Sometimes the requests get immediately routed to the same
clone but there have been cases where 8 requests were necessary
before using the same clone. Selection policy used
is "round robin". Local fixProblem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server Users - Session *
* Manager running in Manual Update Mode *
****************************************************************
* PROBLEM DESCRIPTION: The Session Object is serialized in *
* the manual update mode even though it *
* won't be persisted to the database. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The Session Object is serialized in the manual update mode even
though it won't be persisted to the database. Problem conclusion
The session object is now only serailzed in the manual update
mode when the sync method is called on it. Temporary fix
PQ54710 Comments
APAR information | APAR number | PQ54710 | Reported component name | WAS ADVANCED SU | Reported component ID | 5648C8402 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2001-11-14 | Closed date | 2001-11-30 | Last modified date | 2001-12-25 |
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:
Modules/Macros APAR is sysrouted TO one or more of the following:Modules/Macros
|
Fix information |
Fixed component name | WAS ADVANCED SU | Fixed component ID | 5648C8402 |
Applicable component levels | R350 PSY | UP |
|