Resource Failure Scenarios

JMS Failure

The JMS failure occurs when a connection to the Enterprise Message Service server is not available. The reason could be a connectivity issue with the Enterprise Message Service server, or the Enterprise Message Service server might have stopped. The Enterprise Message Service server can be configured as standalone, or in the fault tolerant mode. In the fault tolerant mode, if the application is not able to get an Enterprise Message Service connection, because of a network issue, it is identified as failure. If all the Enterprise Message Service servers in FT mode have stopped, and are not returning an Enterprise Message Service connection, a failure is triggered.

Additionally, for Enterprise Message Service standalone mode, if the application is not able to get an Enterprise Message Service connection, because of a network issue, it is identified as a failure.

Database Failure

The database failure occurs when a connection to the database server is not available. The reason could be a connectivity issue with database server or the database server might have stopped.

Batch Processor on Error

If the batching is configured, the database notifications are batched, executed and committed in batch. If the transaction fails, each notification from the batch is executed separately and is committed to the database. If the transaction still fails, the batch processor marks the notification as a batch error and the notification is moved to dead letter table in the database. Any other notification for the same order is moved to the dead letter table. The batch processor is marked as an ERROR state if the database sub-batching, or batch task, fails after maximum retries.