Error notification
When an inbound or outbound transaction results in an error in a queue, an email notification is sent to the system administrator only if no other unresolved errors are waiting in the same queue. If multiple errors exist in the queue, the system administrator must resolve all of them before notification of new errors is sent.
An email error message includes a Java™ error stack trace.
The same notification process is used for all errors, queues, and messages, regardless of whether the system is running in a clustered or non-clustered environment.
The following example describes error notification for a continuous inbound JMS queue that contains ten messages. The first four messages are processed successfully and an error occurs on the fifth message. Depending on the value you set for the Maximum Try Count property for the external system, the message can be retried one or more times. If the message does not process successfully, it is moved to either an error queue if one is configured, or to be manually reviewed in the Message Reprocessing application. A notification email is sent to the system administrator and subsequent messages in the queue are processed. If another error occurs in the seventh message, email notification is not sent unless the system administrator resolved the original error. If the system administrator resolved the original error and no errors are pending, a new email notification is sent.
Multiple errors can exist only in the continuous inbound JMS queue. In a clustered environment, the system administrator can receive one email error notification per application server, depending upon the timing of the transactions in error.
The following example describes error notification for a sequential outbound or inbound queue that contains ten messages. The first four messages are processed successfully and an error occurs on the fifth message. Depending on the value you set for the Maximum Try Count property for the queue, the message can be retried one or more times. If the message continues to cause an error, an email notification is sent to the system administrator and subsequent messages in the queue are not processed until the message with the original error is resolved or, if you are using a Kafka provider, the message expires and is deleted from the Kafka queue. The administrator is notified about the first error.
An uncommon exception condition can occur with outbound JMS messages when a message is saved to the queue but the commit of the transaction to the queue fails. This exception can occur because a database connection to the JMS data store is not available. If this exception occurs, a notification is sent and the message in error is visible in the Message Reprocessing application with a status of either JMSERROR or SAVED. Because the message was not saved successfully in the queue, you cannot set the message status to RETRY, but you can process the message from the application.