Fix (APAR): WAS_DRS_03-16-2004_5.0.1_cumulative_Fix Status: Fix Release: 5.0.1 Operating System: All Supersedes Fixes: PQ75365,PQ79680,PQ76091,PQ76310,PQ77785,PQ78045,PQ78204,PQ79243, PQ85234,PQ85318,PQ78005,PQ79072,PQ79493,PQ81536,PQ81990,PQ83816 CMVC Defect: Byte size of APAR: 97141 Date: 2004-03-16 Abstract: Websphere Data Replication Cumulative Fix 5.0.1 03/16/2004 Description/symptom of problem: This is a cumulative fix that is being released for the 5.0.1 product. Fixes to this component will resolve bugs and errors that come up in the HTTP Session Memory to Memory replication function or the Websphere Dynamic Cache replication function. 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 configs 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 Appserver 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. Directions to apply fix: NOTE: YOU MUST FIRST DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX. The Fix Installer can be downloaded from the following link: http://www-3.ibm.com/software/webservers/appserv/support/index.html 1) Create temporary "fix" directory to store the jar file: UNIX: /tmp/WebSphere/fix Windows: c:\temp\WebSphere\fix 2) Copy jar file to the directory 3) Shutdown WebSphere 4) Follow the Fix installation instructions that are packaged with the Fix Installer on how to install the Fix. 5) Restart WebSphere 6) The temp directory may be removed. Directions to remove fix: NOTE: FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED. DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED. YOU MAY REAPPLY ANY REMOVED FIX. Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied. 1) Shutdown WebSphere 2) Follow the instructions that are packaged with the Fix Installer on how to uninstall the Fix. 3) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere 2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix. 3) Restart WebSphere Additional Information: