APAR status
Closed as program error.
Error description
You might see Workflow Server or Workflow Authoring pods cashing due to OutOfMemoryError, and it is not helpful to adjust memory limits in Custom Resource (CR) related component section.
Local fix
Add -Xmx<Target Memory> property to jvm_customizee_options in (CR) for Workflow Server or Workflow Authoring Server settings. see https://community.ibm.com/community/user/automation/blogs/floria n-leybold1/2020/12/17/spot-garbage-collection-overhead-in-baw-on -contain
Problem summary
No additional information is available.
Problem conclusion
A fix is available or will be available that supports to adjust Java heap size dynamically with the changes of K8S memory limits.
Temporary fix
Comments
APAR Information
APAR number
JR63808
Reported component name
CLOUD PAK FOR A
Reported component ID
5737I2300
Reported release
K00
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-06-10
Closed date
2021-07-15
Last modified date
2021-07-15
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
CLOUD PAK FOR A
Fixed component ID
5737I2300
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSBYVB","label":"IBM Cloud Pak for Business Automation"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"K00","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
11 March 2022