PM41746: DATA IS LOST AFTER SETTING IN-MEMORY CONSTRUCTED NODE INTO A STREAMED NODE.

8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• When an unprocessed in-memory node is set inside a streamed node
  the framework might assign an incorrect state to that foreign
   in-memory node which causes it to omit its unprocessed data
  during operations such as serialization.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM Business Process Manager and            *
  *                  WebSphere Enterprise Service Bus customers  *
  *                  using Lazy Parsing Mode                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: Unprocessed in-memory node was being    *
  *                      assigned an incorrect state after it    *
  *                      moved into a streamed node.             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When the foreign in-memory node was moved inside a stream
  node, the framework assigned a particular state which
  prevented unprocessed data inside that foreign node to be
  reached.  This caused loss of data.
  

Problem conclusion

• The state of the foreign node is now properly assigned to
  allow unprocessed data to be reached.
  
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.1.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

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

  PM38726

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

Fix information

• Fixed component name

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R800 PSY