JR47508: CACHED VALUE FOR 'HASXCTIDCOLUMN' POTENTIALLY CAUSES EVENT PROCESSING FAILURES FOLLOWING MODEL DEPLOYMENT/UNDEPLOYMENT

IBM Business Monitor V8.0.1 Fix Pack 2 (8.0.1.2)
IBM Business Monitor V7.5.1 Fix Pack 2 (7.5.1.2)

APAR status

• Closed as program error.

Error description

• Events do not process successfully after monitor model
  deployment or undeployment in the case where some versions of a
  monitor model use scalable event processing while other versions
   of the same monitor model do not use scalable event processing.
  
  The class
  com.ibm.wbimonitor.router.persistence.spi.EventPersistenceManage
  rFactory has a method named hasXctIdColumn and is loaded by the
  Business Monitor class loader.  Once the class is loaded,
  results are held in a cache.  Due to the cached results, event
  processing will not work until the Business Monitor environment
  is restarted.
  

Local fix

• Restart the Business Monitor environment to clear the cached
  value for hasXctIdColumn that is associated with the
  com.ibm.wbimonitor.router.persistence.spi.EventPersistenceManage
  rFactory class.
  
  After restarting the environment and enabling a
  com.ibm.wbimonitor.router.persistence.spi.*=all trace, the
  hasXctIdColumn method will return a "false" value as illustrated
  below.
  
  EventPersiste <
  com.ibm.wbimonitor.router.persistence.spi.EventPersistenceManage
  rFactory hasXctIdColumn Exit: ret=false
  
  After the restart, the correct EventPersistenceManager (such as
  com.ibm.wbimonitor.router.persistence.withoutxct.EventPersistenc
  eManagerImplDB2) will be used and events will be processed
  successfully.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of IBM Business Monitor.              *
  ****************************************************************
  * PROBLEM DESCRIPTION: Events do not process successfully      *
  *                      after a monitor model version is        *
  *                      deployed or undeployed.                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The problem is specific to the case when some versions of a
  monitor model use scalable event processing while other
  versions of the same monitor model do not use scalable event
  processing.  In this case, cached information for
  hasXctIdColumn was not handled correctly.
  

Problem conclusion

• The caching key for hasXctIdColumn was modified to include a
  database table name qualifier so that the cached value is
  relative to the monitor model version level rather than the
  monitor model level.  As a result, events will process
  successfully after monitor model deployment or undeployment in
  cases where some monitor model versions use scalable event
  processing while other versions of the monitor model do not
  use scalable event processing.
  
  An interim fix has been created for IBM Business Monitor
  version 7.5.1.1.
  

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

  WEB BUS MONITOR

• Fixed component ID

  5724M2400

Applicable component levels

• R750 PSY

     UP