Currently, there's no documentation about mixing management and messaging operations in a transaction. The only documentation about transactional processing refers to messaging operations.

I can't seem to figure out how to pass it the proper options to get the Delayed Message Plugin to work properly when using servicebus.

My current attempt is as follows:

Consumer:

  const options = {
      ack: true,
      queueOptions: {
        exchangeOptions: {
          type: 'x-delayed-message',
          'x

DocumentMessage is one of the Enterprise Integration Patters and should be supported as well as the Event Message, [Command Message](http://www.enterpriseintegrationpatterns.com/p

Hi,

I'm believe I'm running into this issue when running make all:

➜  uname -a
Linux stian-Precision-5530 4.18.0-18-generic #19~18.04.1-Ubuntu SMP Fri Apr 5 10:22:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
➜  go version
go version go1.12.4 linux/amd64
➜  pwd
/home/stian/go/src/github.com/Azure/azure-service-bus-go
➜  make all
▶ running

i am trying to register my message Hander for azure servicebus and i see the following description about one of the constructors of messageHandlerOptions class:-
maxConcurrentCalls maximum number of concurrent calls to the onMessage handler
autoComplete true if the pump should automatically complete message after onMessageHandler action is completed. false otherwise.
**maxAutoRenewDurat

Bummer I can't submit a PR to the wiki because of how it works on GitHub, but I pushed my own fork with the addition here.

https://github.com/tdbrian/PlatibusWiki/blob/master/1.-Installation.md#platibusaspnetcore

Platibus.AspNetCore

AspNetCore support is provided in the Platibus.AspNetCore package. This package allows for configuration through ConfigurePlatibus on the IS

• Move parts of readme to wiki
• Write more documentation content
• Write documentation for new powershell WindowsServiceHost installers

Описание ошибки

Шина с RabbitMQ. Отключаются consumer'ы RabbitMQ для отправки в callback-интерфейсы клиентов. Переподключение к RabbitMQ либо не происходит вообще, либо длится очень долго.

Ожидаемое поведение

Consumer'ы должны восстанавливать соединение с RabbitMQ.

Шаги воспроизведения

Алгоритм воспроизведения не известен.

Конфигурация

Поднят стек в докере. Конфигураци