Resource Failure Scenario

JMS Failure

The JMS failure occurs when a connection to the EMS server is not available. The reason could be a connectivity issue with the EMS server, or the EMS server might have stopped. The EMS 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 EMS connection, because of a network issue, it ia identified as failure. If all the EMS servers in FT mode have stopped, and are not returning an EMS connection, a failure is triggered.

Additionally, for EMS standalone mode, if the application is not able to get an EMS connection, because of a network issue, it will be 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.