PI46472: LdapRegistry does not work when the search results cache is defi ned as <searchResultsCache enabled="true" />

8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• A RegistryException is thrown for any function that uses the
  LdapRegistry operation when search results cache is defined
  as <searchResultsCache enabled="true" />. When the cache
  definition is removed, the LdapRegistry works fine.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile- Virtual Member      *
  *                  Manager (VMM)                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: LdapRegistry does not work when the     *
  *                      search results cache is defined as      *
  *                      <searchResultsCache enabled="true" />   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A RegistryException is thrown for any function that uses the
  LdapRegistry operation when search results cache is defined as
  <searchResultsCache enabled="true" />. When the cache definition
  is removed, the LdapRegistry works fine.
  

Problem conclusion

• Modified the code to handle the cache definition when search
  results cache is defined as <searchResultsCache enabled="true"
  />
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 8.5.5.7.  Please refer to the Recommended Updates page for
  delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

• Instead of defining search results cache as <searchResultsCache
  enabled="true" />, define it as <searchResultsCache
  enabled="true" resultsSizeLimit="2000"/>.
  

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

  WAS LIBERTY COR

• Fixed component ID

  5725L2900

Applicable component levels

• R855 PSY

     UP