Data replication component cumulative fix for
V5.0.1, dated 16 April 2004
Downloadable files
Abstract
This component cumulative fix applies to WebSphere®
Application Server V5.0.1. Fixes
to this component resolve issues, bugs, and errors that come up in the
HTTP
Session
Download Description
This fix contains and supersedes the following fixes/APARs:
163603 Fix partition choosing when doing partial partitioning
163611 Fix multiple brokers in a single JVM configurations
165308 PERF enhancement- use obj messages; fix NullPointerExceptions
165271 Exception thrown during deserialization of HomeHandle
PQ75365 JMSMessageQueueOverflowException: using m2m session replication
PQ79680 Data Replication problems if > 2 servers in cluster
PQ76091 Share Type PUSH_PULL in Dynamic Cache fails outside of cluster
PQ76310 NullPointerException when processing received Session
Acknowledgement
PQ77785 Fix improper Data Replication dead server detection
PQ78045 Fix Data Replication to not replicate to same node when using
single replica.
PQ78204 Fix Data Replication bug which broke the Dynamic cache in
Push-Pull mode.
PQ79243 Fix Data Replication round-robin topic load-balancing in 1-replica
mode.
PQ85234 Failover does not occur, new session object is created
PQ85318 Deadlock in Replication, Disthub, Session manager during
Application Server shutdown.
PQ78005 Fix CloseJMS behavior for multiple replication instances in a JVM
PQ79072 Application server startup hangs with > 2 DRS instances
PQ79493 M2m replication fails with EOF Exception.
PQ81536 zOS: Fix resetJMS recovery level functionality
PQ81990 zOS SVT: Miscellaneous Data Replication fixes
PQ83816 Deadlock in com.ibm.disthub.impl.jms.SessionDispatcher on
Appserver recycling.