This project is read-only.

How to setup reliable delivery?

May 16, 2012 at 8:32 AM

Is is possible to create a setup for the following use case?

1. App1 sends a message to Rockbus

2. Rockbus sends a reply to App1 (the reply is defined by a contract)

3. Rockbus routes the message to App2.

if routing the message to App2 fails, Rockbus must retry a number of times (configurable). If sending to App2 fails to many times, some sort of notification to the operator must take place (e.g. sending an email).

Mar 3, 2013 at 10:36 PM
Hi Wouter,

This is definitely possible. RockBus supports several Message Exchange Types:
  • OneWay
  • TwoWayRequestResponse
  • TwoWayAck
The last option is what you are looking for. It means that RockBus will send back to the Publisher an acknowledgment, that the message was received and persisted in the RockBus message store. After the acknowledgement was sent to the Publisher, RockBus takes care of delivery to the subscriber(s).

The notification to the operator is not yet implemented. However, when using the database as the message store, the "dead letter" messages can be found with a sql query. When using MSMQ as persistence store, one could use the MSMQ administration console to find dead letter messages.