IV31569: "RE-REGISTRATION OF THE MESSAGE RECOVERY THREAD ONLY IF SETTINGS HAVE CHANGED"

Version 8.0.1 Fix Pack 1 for the IBM Business Process Manager products
Version 7.5.1 Fix Pack 2 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• "re-registration of the message recovery thread only if settings
  have changed"
  .
  "Currently, every time a Process Server application target JVM
  is re-)started, a re-registration of the Work Manager message
  recovery thread with the BPEScheduler happens (CScopeProvidedBea
  n.reRegisterCleanup()). This requires the cancellation and re-
  creation of a scheduler entry through scheduler APIs. In a dis-
  tributed platform high availability environment or on a multi-
  servant setup on zOS re-registrations can happen multiple
  times (redundantly), due to the number of JVM starts.
  However, generally the re-registration is only required, if the
  configuration settings for th recovery thread have changed.
  have changed. The fix will introduce this conditional re-
  registration, thus greatly reducing the number of re-
  registrations."
  

Local fix

Problem summary

• Problem Description:
  When using WorkManager based navigation, on server restart in a
  clustered environment, the following assertion
  may be observed in SystemOut.log:
  
   Assertion violation !(Cannot schedule Message Cleanup) in
  method >>
  com.ibm.bpe.framework.navigation.CScopeProviderBean.reRegisterCl
  eanup(CScopeProviderBean.java:198)
  
  Problem Summary:
  Currently, every time a Process Server application target
  JVM is (re-)started, a re-registration of the Work Manager
  message
  recovery thread with the BPEScheduler happens
  (CScopeProviderBean.reRegisterCleanup()). This requires the
  cancellation
  and re-creation of a scheduler entry through scheduler APIs. In
  a
  distributed platform high availability environment or on a
  multi-servant
  setup on Z/Os re-registrations can happen multiple times
  (redundantly),
  due to the number of JVM starts. Under unfavorable
  circumstances,
  this can lead to deadlocks and unavailability of the Scheduler.
  
  Problem Conclusion:
  
  Re-registration is only required, if the configuration settings
  for the recovery thread
  have changed. The fix will introduce this conditional
  re-registration,
  thus greatly reducing the number of re-registrations."
  

Problem conclusion

• Problem fixed
  iFix available on top V620 FP3
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  PM76642

• APAR is sysrouted TO one or more of the following:

  JR45336 JR45346 JR45347 IV36142

Fix information

• Fixed component name

  BUS PRC CHOREOG

• Fixed component ID

  5655FLW11

Applicable component levels