BX_INSTANCE_PROCESS_MAX_TASKS_REACHED Audit Message is Not Displayed When a Process Instance Halts on Reaching Its Maximum Tasks Threshold
Article ID: KB0083140
Updated On:
| Products | Versions |
|---|---|
| TIBCO BPM Enterprise (formerly TIBCO ActiveMatrix BPM) | 3.0, 3.1, 4.0, 4.1, 4.2 |
Description
The following ActiveMatrix BPM versions included a fix (WRM-9282) for a problem where a runaway process generated a large number of tasks within a single process instance:
* 3.0.0_HF-004 or later
* 3.1.0_HF-006 or later
* 4.0.0_HF-003 or later
* 4.1.0_HF-005 or later
* 4.2.0
On an ActiveMatrix BPM system with WRM-9282 applied, when the BPM runtime starts to process an event for a process instance, it checks (and increments) how many BPEL tasks the process instance already has. If this value equals or exceeds a configurable threshold value, the BPM runtime halts the process instance and writes the following warning to the BPM log file:
[WARN] - {MAX_TASKS_PER_INSTANCE_REACHED} - Instance [pvm:xxxxx] has reached the maximum number of
tasks allowed: [xxxx]
The BPM runtime should also write the following message to the audit trail:
BX_INSTANCE_PROCESS_MAX_TASKS_REACHED Maximum number of tasks per instance reached.
However, this audit message does not appear unless you have manually added the BX_INSTANCE_PROCESS_MAX_TASKS_REACHED message to the <CONFIG_HOME>\bpm\<bpm_app_name>\configuration\ec-probe-rules.xml file. The description of WRM-9282 in the Hotfix Readme or 4.2.0 Release Notes did not specify that you need to do this.
Consequently, a process instance may halt because it has reached its task threshold value, but the audit trail will not give you any indication that this is what has happened. This problem may affect systems running the following ActiveMatrix BPM versions:
* 3.0.0_HF-004 or later
* 3.1.0_HF-006 or later
* 4.0.0_HF-003 or later
* 4.1.0_HF-005 or later
* 4.2.0, if you have upgraded to it from version 3.1, 4.0 or 4.1 (irrespective of the Hotfix level of the
3.1, 4.0 or 4.1 system).
NOTE: This issue does not occur on a newly installed ActiveMatrix BPM 4.2.0 system.
Environment
Resolution
2. Open the file in a text editor and find the <messageIds> section of the AuditMessages rule.
For example:
<rule name="AuditMessages" ruleOrder="800">
<filter>
<severities>
<severity>AUDIT</severity>
</severities>
<messageIds>
<messageId>BX_INSTANCE_TASKS_CREATED</messageId>
<messageId>BX_INSTANCE_TASKS_COMPLETED</messageId>
...
</messageIds>
3. Add the following line to the <messageIds> section (if it is not already there):
<messageId>BX_INSTANCE_PROCESS_MAX_TASKS_REACHED</messageId>
4. Save and close the file.
The BPM runtime monitors this file dynamically, so the change takes effect as soon as the file is next checked. You do not need to restart any component of the ActiveMatrix BPM system.
If a process instance halts because it has reached its task threshold value, the correct message:
BX_INSTANCE_PROCESS_MAX_TASKS_REACHED Maximum number of tasks per instance reached.
will be displayed in the audit trail.
Issue/Introduction
Additional Information
Feedback
