IBM Support

How do I resolve the error "Re-execute limit reached..."?

Question & Answer


Question

How do I resolve the error "Re-execute limit reached..."?

Answer

On Demand Consulting
Author: Sila Kissuu

In general, this error occurs in exceptional situations within the Event Manager , such as a "queue full condition" of the monitor event queue.?

The Event Manager is responsible for scheduling and driving the execution of work in Process Server/Process Center including execution of Business Process Definitions(BPDs), invocation of BPD system task implementations and BPD timer events. This is accomplished via Event Manager tasks. The diagram below illustrates how the Event Manger processes incoming messages/events:


When exceptions occur during processing failed tasks are queued up for re-execution to mitigate the exception. The default number of tries is 5. Default runtime configuration settings for the Event Manger can be found in the 80EventManager.xml.
NOTE: Do not directly edit this file but rather use the 100Custom.xml file to adjust settings (see the IBM BPM Knowledge Center for more information on how to change configuration properties). After 5 failed attempts to re-try a task is put on hold and flagged in the database thus making it eligible to be rescheduled to be run in the future with the BPMReplayOnHoldEMTasks command. While on hold the associated process instance might stop responding.

The "Re-execute limit reached" error has been observed in a number of scenarios including:

  • Monitor events being?generated at a rate faster than the Event Manager can consume and process.?
This could be indicative of sub-optimal throughput at the Event Manager due to low capacity settings for internal queues in?80EventManager.xml or 100Custom.xml.??
  • The Event Manager in the destination system?not being paused during migration of?process instances.
This causes the?currently migrated tasks to run immediately and?before the migration process has completed.?Since the aggregate state of the set of?process instances in the source runtime is not?completely restored/known in the destination runtime errors are bound to occur and trigger re-tries in the Event Manager. Ensure the Event Manager in the destination system is configured to start in a paused state:?<start-paused>false</start-paused>

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSQTW3","label":"IBM On Demand Consulting for Hybrid Cloud"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
17 March 2019

UID

ibm10778515