You can use correlator diagnostic output to identify slow or blocked receivers.

Bad receivers include:

When the correlator’s output queue fills, operations that are sending events from the processing thread (or threads, if there is more than one context) are blocked. If the output queue remains filled, and the processing thread(s) remain blocked, the input queue(s) start(s) to fill. Events are never dropped.

If you specify the -x correlator option when you start the correlator, it causes the correlator to disconnect any receiver that becomes bad. If you discover that your application is producing events at too high a rate for a particular receiver you might be able to publish the events to separate channels so that the receiver needs to handle fewer events. Alternatively, or in addition, you might be able to modify your application to throttle the rate at which it sends events to this receiver.

If you cannot speed the receiver up, or install faster hardware, you can partition the correlator’s output event flow into channels so that the receiver needs to handle fewer events. Alternatively, you can use throttling in the correlator to output events less frequently.

See also Determining whether to disconnect slow receivers, in the "Event Correlator Utilities Reference" section of Deploying and Managing Apama Applications.