How To
Summary
This workaround is in place for customers who observe STOMP timeouts within their logs and a large delay of time between the processing of jobs. During our investigation, we found there are performance impacts when many messages with large payloads are processed at once. This is due to the resilient-circuits prefetch size limit and the value that the limit is defaulted to: 20. The default value of 20 is too large for the quantity of messages being processed, so this value needs to be reduced. A fix for this issue that does not require any code changes to Resilient or Resilient-circuits and improves the STOMP timeout issue experienced by customers follows. If an integration is updated, the prefetch value will be removed from the app.config and will need to be re-added.
Document Location
Worldwide
Log InLog in to view more of this document
Was this topic helpful?
Document Information
Modified date:
19 April 2021
UID
ibm11283518