PK24649: DATA REPLICATION SERVICE NOT CORRECTLY HANDLING ERRORS

6.1.0.1: WebSphere Application Server V6.1.0 Fix Pack 1 for HP-UX
6.1.0.1: WebSphere Application Server V6.1.0 Fix Pack 1 for AIX
6.1.0.1: WebSphere Application Server V6.1.0 Fix Pack 1 for Windows
6.1.0.1: WebSphere Application Server V6.1.0 Fix Pack 1 for Linux
6.1.0.1: WebSphere Application Server V6.1.0 Fix Pack 1 for i5/OS
6.1.0.1: WebSphere Application Server V6.1.0 Fix Pack 1 for Solaris

APAR status

• Closed as program error.

Error description

• DRS does not correctly handle errors during serialization when
  sending a message.
  
  DRS catches the NPE but still sends the message
  
  FFDC shows
  [5/5/06 17:35:51:582 EDT] 0000004a HttpSessDRSBu 3
  storeObject: Caught
  Exception while trying to serialize.
  then when DRS is invoked:
  [5/5/06 17:35:51:729 EDT] 0000004a DRSBuffWrappe 3
  storeObject:
  Exception while trying to serialize,
  t=java.lang.NullPointerException
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of WebSphere Application Server    *
  *                 version 6 using HTTP Session memory to       *
  *                 memory, EJB stateful session beans or        *
  *                 Dynamic Cache replication.                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Replication service does not correcly   *
  *                      handle errors during message            *
  *                      serialization.                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The replication service serializes messages that are sent to
  other replication service servers. If the serialization fails
  the replication service is still sending the message to the
  other servers. The partner server will attempt to deserialize
  messages received from other servers. The deserialization
  will fail if the message was not successfully serialized.
  

Problem conclusion

• Messages that do not serialize successfully are no longer sent
  to partner servers.
  
  The fix for this APAR is currently targeted for inclusion
  in 6.0.2.13 and 6.1.0.1.
  Please refer to the recommended updates page for delivery
  information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  
  
  An iFix for this problem was made availabel for the WebSphere
  Application Server 6.0.2 release.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• DRS
  

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R60A PSY

     UP

• R60H PSY

     UP

• R60I PSY

     UP

• R60P PSY

     UP

• R60S PSY

     UP

• R60W PSY

     UP

• R60Z PSY

     UP

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP