JR52099: ShippingModeCache returns incorrect shipping modes when there are two concurrent cache misses for different stores

APAR status

• Closed as program error.

Error description

• In a multiple esite environment,
  ShippingHelper.getAllowableShippingModes() call starts to return
   shipping modes for another store_id. Restarting the server as
  well as clearing ShippingModeCache fixes the issue.
  

Local fix

• The frequency of this error can be reduced by disabling the
  ShippingModeCache logical data cache, by adding the following
  configuration to the CrossTransactionCache tag in the
  InstanceProperties tag in the wc-server.xml instance
  configuration file:
  
  <CrossTransactionCache ..... >
  ...
  <com.ibm.commerce.fulfillment.objsrc.ShippingModeCache
  enabled="false" />
  ...
  </CrossTransactionCache>
  

Problem summary

• USERS AFFECTED:
  All WebSphere Commerce customers for Versions 6 and 7 with
  WebSphere Commerce instances that provide more than one store.
  
  PROBLEM ABSTRACT:
  ShippingModeCache returns incorrect shipping modes when there
  are two concurrent cache misses for different stores
  
  BUSINESS IMPACT:
  This only happens when more than one store is used concurrently.
    A shopper could encounter an error, or be offered incorrect
  shipping modes.
  
  RECOMMENDATION:
  

Problem conclusion

• A programming error was corrected.
  

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

  5724I3800

Applicable component levels

• R700 PSY

     UP