IMPROVED Session replication and persistence using the WebSphere Data Replication Service

Recently we have improved the performance and footprint of session serialization and deserialization code when failover occurs in WAS.  Issues like session replication causing  OOM have been fixed by APAR 

PM38550: OUTOFMEMORY DURING FAILOVER WITH MEMORY-TO-MEMORY SESSION REPLICATION. 

When the fix is enabled by setting the JVM custom property DRS_BATCH_INTERVAL_SIZE to 50.  The DRS service will replicate HTTP session data in multiple batches of 50 objects in each batch. 

This fix basically chunks the updates sent by one WAS server to another thereby leading to a reduced heap footprint as serialized byte[] are not buffered till the entire object is in memory.

I suggest enabling this custom property for faster and more efficient serialization of your HTTP sessions  with WebSphere Application Server