IV73834: Cache invalidation is not triggered after BCS context data is persisted, resulting in an activity finder exception.

JR53438 - Mandatory cumulative Interim Fix for WebSphere Commerce Version 7 Fix Pack 9
JR55049 - Mandatory cumulative Interim Fix #3 for WebSphere Commerce Version 7 Fix Pack 9
JR57861 - Mandatory cumulative Interim Fix 5 for WebSphere Commerce Version 7 Fix Pack 9

APAR status

• Closed as program error.

Error description

• Cache invalidation is not triggered after context data is
  persisted, resulting in an activity finder exception.
  
  Example:
  The following finder exception has occurred during processing:
  "5104471709".
  
  This problem occurs when custom code attempts to read the BCS
  session data in the same database transaction in which it was
  created.
  

Local fix

Problem summary

• USERS AFFECTED:
  Client who has custom code attempting to read the BCS session
  data in the same database transaction in which it was created.
  
  PROBLEM ABSTRACT:
  Cache invalidation is not triggered after BCS context data is
  persisted, resulting in an activity finder exception.
  
  BUSINESS IMPACT:
  Varies depending on the customization. Typically storefront
  request where user (shopper) is updated during the transaction.
  
  RECOMMENDATION:
  

Problem conclusion

• Cache invalidation is performed immediately after the new
  session data is created, as well as after the current
  transaction completes.
  

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:

Fix information

• Fixed component name

  WC BUS EDITION

• Fixed component ID

  5724I3801

Applicable component levels

• R600 PSY

     UP