1.7.4

As part of this release we had 1 issue closed.

Bug fixed

#583 When using RabbitMQ, failed messages sent for reprocessing have callback address header set to SC's callback receiver

On RabbitMQ transport when a message is retried, the transport dispatcher adds the callback address header (its own, pointing to SC's callback queue). If the handler for the retried message uses Bus.Reply, the callback address is used (instead of reply_to property) which results in sending the reply to ServiceControl callback input queue instead of the endpoint which send the original message.

Where to get it

You can download this release from our website