JR63170: APPLICATION ENGINE RESTARTS UNEXPECTEDLY

APAR status

• Closed as program error.

Error description

• Because unnecessary Redis clients are created during the IBM
  Application Engine readiness probe, the maximum number of Redis
  clients allowed might be reached, causing Application Engine to
  restart.
  
  The following is an example of error you might see in the
  Application Engine log before the Application Engine restarts:
  
  {"level":50,"time":1607958188317,"pid":42,"hostname":"icp4adeplo
  y-workspace-aae-ae-deployment-79b5dcbcf4-nwmbr","file":"server",
  "msg":"readinessProbeAbortError: Ready check failed: Redis
  connection lost and command aborted. It might have been
  processed.","v":1}
  {"level":50,"time":1607958188540,"pid":42,"hostname":"icp4adeplo
  y-workspace-aae-ae-deployment-79b5dcbcf4-nwmbr","file":"server",
  "msg":"readinessProbeReplyError: ERR max number of clients
  reached","v":1}
  
  PRODUCTS AFFECTED
  IBM Cloud Pak for Automation - Business Automation Application
  IBM Cloud Pak for Automation - Business Automation Studio
  

Local fix

Problem summary

• No additional information is available.
  

Problem conclusion

• A fix is available or will be available that ensures the
  Application Engine readiness probe doesn't create unnecessary
  Redis clients.
  

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

  CLOUD PAK FOR A

• Fixed component ID

  5737I2300

Applicable component levels