Troubleshooting the BPMN event emitter

To better follow up the activity of the BPMN event emitter, you can enable tracing. If events are not flowing to the JMS queue or to Kafka, use the check lists to ascertain proper JMS configuration.

Enabling tracing on the BPMN event emitter
You can enable detailed tracing of the BPMN event emitter by adding a package to the trace definition in the WebSphere® Application Server administration console.
Resolving events not flowing to the JMS queue
If you observe that no events are flowing Kafka, the cause might be with the JMS queue. Check the DEF configuration, the status of the messaging engine, and the configuration of the Java™ Message Service (JMS) resources.
Resolving events flowing to the JMS queue but not to Kafka
If you observe that events are flowing to the JMS queue but not to Kafka, check whether the BPMN event emitter application is installed, whether the emitter is not paused, and whether events are retried after a JMS exception.
Troubleshooting JMS destination issues
If you observe that events are flowing to the JMS queue but not to Kafka, after you have checked whether the BPMN event emitter application is installed and started, and that the emitter can consume events from the JMS queue, you check that events are retried after a JMS exception. If the JMS destination setting causes error messages, you can check more configuration elements.

Parent topic: Troubleshooting