Skip to content

Limits

Delivery

  • A publish is never deduplicated. A publish retried after an ambiguous failure can be stored and delivered twice. Handlers must be idempotent. See How a publish travels.
  • ExtendLease can still deliver twice. When the lease reaches MaxProcessingTime, the message is handed on while a handler may still hold it. LeaseExpired counts it.
  • A decline is redelivered at once. There is no delayed redelivery; see Capabilities.
  • No replay. A new durable name sees what the queue holds, not what came before the queue.
  • No request and reply.
  • No overflow policy. ShedNewest and ShedOldest degrade to the native behaviour.
  • AtMostOnce drops what the broker has already delivered. With automatic acknowledgement, a message received when the connection drops or the source retires is not redelivered. An unreadable message under AtMostOnce is dropped.

Connection

  • The adapter has no reconnection code. Open dials once and the session uses one connection. When the broker cancels a consumer or closes its channel, that source ends with a cause. Whether the core resubscribes is the core's behaviour; a lost connection is not repaired by the adapter.
  • The management API is a hard dependency. It must be enabled, reachable and authorised for the queue paths. A subscription's first verification can wait up to 15 seconds for the API's statistics to appear. Each management request has a 10 second timeout.
  • Heartbeats, TLS settings and dial timeouts are amqp.Dial's defaults. There is no setting for them; amqps:// is accepted in URL.

Topology

  • Operator-owned. Nothing durable is created. See Topology it expects.
  • The dead-letter exchange is checked for being set, not for existing. A message dead-lettered to an exchange with no bound queue is lost by the broker's rules, not the adapter's.
  • A consumer timeout set only by the node is invisible to the check. If the API reports none for the queue, MaxProcessingTime is not compared with anything.
  • A pattern is a queue's binding. Changing a subscription's Pattern on an existing queue, or raising MaxDeliver past what the queue's delivery limit allows, is refused.
  • Only the first value of a multi-valued header is written. The AMQP headers table carries one string per key here.
  • Only string headers are read. The broker's x-delivery-count and x-death, and any other non-string entry, are not offered to a format and not carried to Foreign.

The lease

  • The timer starts when the adapter receives the delivery, not when a handler begins. A delivery waiting for a free handler spends its lease while it waits.
  • Bound is the prefetch. The adapter's buffer holds Bound - 1 deliveries.

Versions

  • Tested against RabbitMQ 4.3.5 only. See Tested versions. The doc comment on New says one constructor serves 3.x and 4.x; no fixture checks 3.x.
  • Pre-1.0. The API can change in a minor release.