Event sequencing and multi-threaded processing for the JMS event emitter
You can prevent events from processing out of order by configuring the JMS event emitter to be single-threaded or, more reliably, by having a well-defined sequence field in the event XML payload.
- If you are emitting events from IBM Business Monitor V8.5.5, you use monXMLEventEmitterInputAS.
- If you are emitting events from an earlier version of IBM Business Monitor, and the events are in Common Base Event format, you use MonitorEventEmitterActivationSpec.
By default, the activation specification is configured to be single-threaded. This configuration ensures that events are processed in order even without a well-defined sequence field in the event XML payload.
However, if you have a well-defined sequence field in the event, you can improve performance by setting the activation specification configuration to multi threaded.
- In the WebSphere® Application Server administrative console, select .
- Select the activation specification that applies (monXMLEventEmitterInputAS or MonitorEventEmitterActivationSpec).
- Set the maximum concurrent MDB (message-driven bean) invocations per endpoint to a number greater than 1.
- Restart the server.
To configure the activation specification to multi-threaded, you must ensure that event sequencing is enabled in your monitor model. Then, if sequence information is available in the event XML and reordering is enabled on the server, the server reorders events. For information about how to define the event sequence, see the related information.
If an event is not emitted successfully, the XML is placed in an error queue. For information about how to handle the events in this error queue, see the related reference.