APAR status
Closed as program error.
Error description
Two replication instances are created in one JVM. Only the
first instance pings other equal instances. The second
instance does not execute a ping and eventually becomes
stale. This incorrectly marks this second instance down.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of the Websphere Application *
* Server using Session Manager *
* memory-to-memory replication. *
****************************************************************
* PROBLEM DESCRIPTION: Replication instances incorrectly *
* flagging their peer instances as down *
* causing replication failures *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Multiple components within an Application Server create
multiple replication service instances for the purpose of
memory-to-memory replication. This problem occurs when
one replication service instance's view of the other instances
becomes inconsistent due to faulty ping function.
Problem conclusion
This APAR contains a fix for the faulty ping function causing
the failure. It is targetted to be available as part of
5.1.0.5 and 5.0.2.7.
Temporary fix Comments
APAR information |
APAR number |
PQ88868 |
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 |
2004-05-14 |
Closed date |
2004-07-08 |
Last modified date |
2004-07-08 |
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 |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|