JR42142: CMVC 219475 - ISSUE INVALIDATIONS FOR SERVLET CACHE INSTANCES OTHER THAN BASECACHE INSTANCE.

7.0.0.9 for Developer Express
7.0.0.9 for Developer Professional
7.0.0.9 for Developer Enterprise
7.0.0-WS-WCServer-FP009
WebSphere Commerce Version 7.0.0.7 Fix Pack
WebSphere Commerce Version 7.0.0.9 Fix Pack

APAR status

• Closed as program error.

Error description

• Currently, DynacacheInvalidation scheduler job does not have the
  capability to issue invalidations for servlet cache instances
  other than baseCache instance.
  

Local fix

Problem summary

• USERS AFFECTED:
  Customers of WebSphere Commerce version 7 who define their own
  servlet cache instances and wish to use the
  DynaCacheinvalidation scheduler job to send invalidation id
  strings to their servlet cache instance.
  
  PROBLEM ABSTRACT:
  Adding capability to use the WebSphere Commerce
  DynaCacheInvalidation scheduler job to send invalidation ID
  strings to customer defined servlet cache instances.
  
  BUSINESS IMPACT:
  Since DynacacheInvalidation job is not enabled to send
  invalidations to custom servlet cache instances, this limitation
  is an obstacle in getting performance benefits of custom defined
  servlet cache instances
  
  RECOMMENDATION:
  

Problem conclusion

• The IBM WebSphere Commerce DynaCacheInvalidation scheduler job
  looks in the CACHEIVL table for recently added rows.  When it
  finds a value in the TEMPLATE column that starts with "cmd:" it
  uses the rest of the value following the "cmd:" prefix as a java
  class name.  If the specified java class is not an instance of
  com.ibm.commerce.dynacache.commands.StringHolderCmdImpl, no
  action is taken.  However, if the specified java class is an
  instance of a subclass of
  com.ibm.commerce.dynacache.commands.StringHolderCmdImpl, then an
  instance of that class is created, its setString method is
  called passing the value of the DATAID column, and the command
  instance is executed.
  
  A custom servlet cache can cause the specified DATAID value to
  be sent as an invalidation to a servlet cache instance by
  specifying that command in the cachespec.xml file for the custom
  servlet cache instance.  For example:
  
  <cache-instance name="instance2">
   <cache-entry>
   <class>command</class>
   <name>com.ibm.commerce.dynacache.commands.StringHolderCmdImpl</
  name>
   <invalidation>
    <component type="method" id="getString">
    </component>
   </invalidation>
   </cache-entry>
   <!--
  ****************************************************************
  *********** -->
   <!-- * Place the cache-entry tags for the servlet cache
  instance here. * -->
   <!--
  ****************************************************************
  *********** -->
  </cache-instance>
  
  Since the same command cannot be defined for more than one
  servlet cache instance, this iFix also includes three sub
  classes of
  com.ibm.commerce.dynacache.commands.StringHolderCmdImpl that can
  be used in the same way to cause invalidations in custom servlet
  cache instances.
  
  com.ibm.commerce.dynacache.commands.StringHolder1
  com.ibm.commerce.dynacache.commands.StringHolder2
  com.ibm.commerce.dynacache.commands.StringHolder3
  
  -------------------------------------------------------------
  The latest available maintenance information can be obtained
  from the Recommended Fixes for WebSphere Commerce technote:
  http://www.ibm.com/support/docview.wss?rs=3046&uid=swg21261296
  

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