Handling events that the JMS event emitter did not emit
When the JMS event emitter does not successfully emit events, you can view and manipulate the events in the error queue.
MDBEmitter E com.ibm.wbimonitor.mdbemitter.MDBEmitter onMessage(Message message) CWMDS6902E: The following exception occurred when processing the XML and sending a Common Base Event ... When the JMS event emitter does not successfully emit events, the events are routed to the SI Bus Destination Queue named MonitorEventEmitterErrorQueue. Check the SystemOut.log of the server where the IBM_WBM_EMITTER_SERVICES application is deployed for errors that indicate why event emission failed. When the problem is resolved, events in this error queue should be reassigned to the SIB Destination Queue named MonitorEventEmitterQueue, where they are automatically processed by the JMS event emitter.
Viewing and manipulating events in the error queue
Use one of the following methods to view and manipulate events in the error queue:
- To view the content of the error queue, use a tool such as SIB Explorer, which is available and free from Alpha Works at http://www.alphaworks.ibm.com/tech/sibexplorer.
- To reassign events from the MonitorEventEmitterErrorQueue back to the MonitorEventEmitterQueue, use a tool such as SIBus Destination Handler, which is available from http://www.ibm.com/support/docview.wss?uid=swg24021439.
- Alternatively, you can use your own application to reassign events from the MonitorEventEmitterErrorQueue back to the MonitorEventEmitterQueue.
By default, the SIBus is configured to retry an event five times before routing it to the error queue. You can use the WebSphere® Application Server administrative console to configure the number of times to retry the event before routing it to the error queue.
