JR55318: Multiple cache entries for each new search request

APAR status

• Closed as program error.

Error description

• For Page Load and Page Refresh, two search requests are
  performed for every new search. Both REST calls are cached
  separately in the WebSphere Commerce search server.
  
  The two search requests have different parameters for
  searchSource and facetLimit when both parameters are empty.
  The expectation is that the second search REST call uses the
  first cache entry and there should not be any parameter
  differences.
  

Local fix

Problem summary

• USERS AFFECTED:
  WebSphere Commerce Version 7.
  
  PROBLEM ABSTRACT:
  Multiple cache entries for each new search request
  
  BUSINESS IMPACT:
  WebSphere Commerce environment saves more cache entries than
  necessary for each search request.
  
  RECOMMENDATION:
  

Problem conclusion

• Added a default value for the searchSource parameter if the
  searchSource parameter is not defined in the call. Furthermore,
  modified code to ensure that the facetLimit parameter is
  excluded from REST service calls if the value is empty.
  

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