Fixes are available
APAR status
Closed as fixed if next.
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
Temporary fix
Comments
APAR Information
APAR number
JR45347
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
801
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-01-10
Closed date
2013-02-06
Last modified date
2013-02-06
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 ADVANCED
Fixed component ID
5725C9400
Applicable component levels
R801 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
12 October 2021