Fixes are available
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
When using the peer-to-peer topology of memory-to-memory session replication with 2 cluster members, the replication domain will be down if 1 of 2 server is down. If the request that is affined to the server comes to the web server, the web server plug-in will send the request to the other server. If the plug-in adds the internal $WSFO flag into the request header for the other server to prevent the stale session data from returning to the client, the user will fail to get the session because the session manager will try to retrieve the session from the original server that is down although the other server already has the copy of session. Need the option to ignore the $WSFO flag if the replication is down. With the option, the user can choose whether the application can get the session in the backup server or don't use the session to prevent the possible stale data from returning to the client.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server full * * profile version 8.0 and 8.5.5 customers * * using memory-to-memory session * * replication. * **************************************************************** * PROBLEM DESCRIPTION: When session replication is down, * * session manager fails to retrieve the * * session during failover. * **************************************************************** * RECOMMENDATION: * **************************************************************** When failover occurs, session manager will attempt to go to the backend to retrieve the latest copy of the session. In most situations, this behavior is desirable because the possibility of stale session data on failover is reduced. However, in cases where the replication domain is down, this would mean session information already present in memory would be removed.
Problem conclusion
The session manager has added a new custom property, IgnoreWSFOHeaderIfReplicationDown (default=false). Set this property to true to allows the session manager to retrieve the session from the local memory instead of the backup server when session replication is down. The fix for this APAR is currently targeted for inclusion in fix packs 8.0.0.9 and 8.5.5.3. Please refer to the Recommended Updatespage for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PI07361
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-12-04
Closed date
2014-03-07
Last modified date
2014-03-07
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
28 April 2022