JR47574: UCAs FROM OLD AND DEACTIVATED SNAPSHOTS STILL FIRING AFTER INSTALLING THE IFIX FOR JR41966

Download Version 8.0.1 Fix Pack 2 for the IBM Business Process Manager products
Version 8.5.0 Fix Pack 1 for the IBM Business Process Manager products
Version 7.5.1 Fix Pack 2 for the IBM Business Process Manager products
Version 8.5 Refresh Pack 5 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• Before JR41966, BPM 7510 contained the problem that scheduled
  UCAs were not cancelled correctly when new default snapshots
  were defined. Rather, duplicate instances of scheduled UCAs were
   created. JR41966 fixed this problem so that no new duplicate
  UCAs were created. However, JR41966 doesn't clean up remaining
  'old' duplicate UCAs.
  .
  One still sees the issue with the duplicate tasks. Triggering
  UCA does update LSW_EM_TASK_KEYWORDS and LSW_EM_TASK but does
  not delete duplicate UCA entries from LSW_EM_TASK.  That is why
  the old and deactivated UCAs fire.
  
  This IFix solves this problem - it cleans up duplicate UCAs that
  were created erroneously by 7510 code before JR41966.
  

Local fix

Problem summary

• The problem is caused by a bug in 7510. A scheduled UCA is
  represented in the database by an entry in LSW_EM_TASK table
  and 2 entries in LSW_EM_TASK_KEYWORDS table. When a scheduled
  UCA was cancelled, the entries in LSW_EM_TASK_KEYWORDS were
  deleted, but the code failed to delete the entry in LSW_EM_TASK.
  Once a task without associated keywords existed, it wasn't any
  more possible to cancel this task, since all task manipulation
  happens via the associated keywords.
  
  PROBLEM DETAILED DESCRIPTION:
  On 7510, the same scheduled UCA could be scheduled multiple
  times when multiple snapshots of a process app contained this
  UCA. On modification of the default snapshot, the 'old'
  scheduled UCA was not cancelled but a new one was scheduled.
  This problem was solved with JR41966.  After installation of
  JR41966, or migration to 7511, 'old' UCAs are cancelled when an
  UCA is disabled or another snapshot is made default.  However,
  there may be remaining scheduled UCAs in the database that were
  created with the pre-JR41966 code level and these UCAs cannot
  be cancelled.
  

Problem conclusion

• The fix for the problem introduces self-healing behavior: Once
  BPM detects that it is about to execute a scheduled UCA task
  that has no associated keywords, it skips execution of this
  task, deletes it and refrains from rescheduling it. In this
  way, the duplicate scheduled UCA tasks disappear silently once
  their schedule time arrives.
  
  Caution: Due to the bug that existed in 7510 and before and was
  fixed with JR41966, there may be UCA tasks in the LSW_EM_TASKS
  table that are expected to be there, but don't have associated
  keywords. These UCA tasks will be removed by this IFix.  If
  this happens, then you can reenable these UCAs by going to the
  Process Admin Console, panel Process application> -> Exposing
  -> UCAs and disabling and reenabling the checkbox for these
  UCAs.
  
  
  FIX AVAILABILITY:
  iFix for 7.5.1.1 is available on Fix Central, search for APAR
  JR47574 at http://www.ibm.com/support/fixcentral/
  Fix is also targetted for inclusion in next fixpack for BPM
  V7.5.1, BPM 8.0.1, BPM 8.5.0
  
  When obtaining any of the above fixes, be sure to download the
  accompanying readme, for itself, and any prerequisite fixes, and
  review them thorougly.
  

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

  BPM STANDARD

• Fixed component ID

  5725C9500

Applicable component levels

• R751 PSY

     UP