Description:
TIBCO BusinessWorks ProcessMonitor (BWPM) Client blocks the TIBCO BusinessWorks (BW) engine when TIBCO Enterprise Message Service (EMS) server is down or not responding. This issue is encountered when the internal queue (maxQueueLength) value is exceeded. The maxQueueLength is a setting for the internal queue of the BWPM Client, which is a kind of pipeline for internal job elements and cannot be compared with the number of BW jobs created. It has no relation with BW jobs queues.

When the TIBCO BusinessWorks ProcessMonitor (BWPM) Client blocks the TIBCO BusinessWorks (BW) engine, BW jobs are created based on incoming requests or messages, but jobs are not completed. BW jobs are seen in an active state in the Admin GUI. There will no log entries recorded in the BW engine logs and no BWPM event messages are publish.

In BWPM 2.x.x, there is no mechanism to identify or monitor whether the BW engine is blocked as no log entries are recorded in the engine log file. In BWPM 3.0.0, the BWPM Client will log the entry, "max queue length exceeded", which indicates that the BW engine is blocked. Using a Hawk rule can identify if the BW engine is blocked or not.

How to identify/monitor that a TIBCO BusinessWorks ProcessMonitor (BWPM) Client has blocked the TIBCO BusinessWorks (BW) engine when the TIBCO Enterprise Message Service (EMS) server is down.