Protecting an MDB application from system resource problems
You can configure the system so that if there is a problem with a dependent external system resource, the enterprise application is stopped before messages are moved unnecessarily to an exception destination. This configuration also handles occasional problems with messages without blocking the enterprise application.
Before you begin
The destination to which the MDB listens must use an exception destination. This exception destination can be the system default, or one configured specifically for the destination.
- The enterprise application that contains the MDB.
- The dependent external system resources.
- An acceptable value for the 循序失敗訊息臨界值, that is, the maximum number of sequential failures of delivery of messages, after which the MDB is stopped. This property applies to sets of messages.
- An acceptable value for the 失敗訊息重試的延遲間隔, that is, the time in milliseconds before a failing message is available to be delivered to the MDB. Other messages might be delivered during this period, unless the 循序失敗訊息臨界值 and the maximum concurrency is set to 1.
- An acceptable value for the 每個訊息的失敗遞送次數上限, that is, the maximum number of failed attempts to process a message, after which the message is forwarded from its intended destination to the exception destination. This property applies to individual messages.
About this task
- Failed messages are retried a finite number of times, and if they continue to fail, they are moved to an exception destination allowing subsequent messages to be processed.
- Failed messages are retried indefinitely until the problem is rectified.
Configuration (1) protects the MDB from an occasional problem message that prevents subsequent messages from being processed. However, if there is a prolonged problem with a resource that the enterprise application or business-level application depends on, for example a database, all messages that are sent to the destination might be moved to the exception destination.
Configuration (2) blocks the delivery of messages until the original failing message problem is resolved. This configuration prevents messages being moved unnecessarily to an exception destination, but it also blocks subsequent messages as soon as a single problem message fails to be processed.
You can configure the activation specification for an MDB so that the MDB endpoint is stopped automatically when a number of failures with sequential messages are detected. These failures indicate a problem with a dependent resource. When the problem is resolved, the MDB endpoint is restarted manually. This configuration tolerates occasional message failures, allowing individual problem messages to be moved to the exception destination without blocking the entire MDB.
Use the following steps to protect an enterprise application from dependent external system resource failures.