Checklist

• I have checked the issues list
  for simi

Is it possible to generate a new event like queue.purged whenever a queue is purged by the user?. The event can include information like who purged the queue, at what time, number of messages purged, vhost name of the queue.

Currently if machinery is misconfigured for the connection to AMQP it will run indefinitely at a exponential backoff. It will be easier for users to detect failure in a production application if the application is allowed to exit out on failures that are not likely going to be recoverable.

There is a lot of supported AMQP features but documentation is missing. People keep asking how to use this library using github issues but this way is no go.

Would be nice to have a brief summary about all main features and use cases in some "Read the docs" style documentation.

Here are things I would like to have documented:

Exchange types and how to declare them:

• simple direct

Reading the documentation for the Consume method in the AQMP module.

I came across this (I think in reference to the nolocal parameter):

It's advisable to use separate connections for Channel.Publish and
Channel.Consume so not to have TCP pushback on publishing affect the
ability to consume messages, so this parameter is here mo

Is your feature request related to a problem? Please describe.
I got few migrations each referring a different connection. migrate:fresh, migrate:refresh doesn't handle this scenario since they operate on the default connection or in the specific connection passed via --database param.

Describe the solution you'd like
The simplest solution can be to process only migrations that has th

We use http_server as input and http_client as one of outputs (for a part of message batch). In case when there is some error coming from http_client, benthos starts to retry this error message indefinitely (#415). However most significant, is that it stops accepting other, normal messages.

Here is the log when I first try to send message which causes http_client to get 500 error, and

I stumbled across <interaction> and ts_interaction_server, but I'm not sure what the use case is or how it is supposed to be used.

Has anyone used this recently and can add some documentation? Or explain to me how this works and I'll write something.

/cc @nniclausse

When the queue workers are restarted (using supervisor), all delayed messages are instantly triggered, regardless of the remaining delay.
This happens when using either rabbitmq_dlx or rabbitmq_delay_plugin delay strategy.

Implemented via laravel-queue with amqp+rabbitmq dsn.

See ruby-amqp/bunny#579 for background.

RabbitMQ Java client has tweaked its "known entity" tracking to track and invalidate entries in its cache of known entities based on some of their attributes for operations that are performed on the same connection (but any channel on that connection).
In other words, if a queue was declared on one channel but deleted on another

The README of the 2.0.0 examples hasn't been updated with the release: https://github.com/asyncapi/asyncapi/blob/master/examples/2.0.0/README.md. We should update accordingly or remove it.

I have error when try delay 30 days in AMQP Interop driver and enqueue/amqp-bunny transport
and rabbit with installed RabbitMQ Delayed Message Plugin. After inspect code and documentation i discover what rabbitmq delayed message plugin max delay is 2^32 milliseconds (~50 days) and bunny have limit for headers 2^31 milliseconds (~25 days)

Hello! If I'm not wrong I found a typo in Introduction section.
https://aio-pika.readthedocs.io/en/latest/rabbitmq-tutorial/1-introduction.html
You mentioned several time and listed in code snippet that in sender.py queue must be declared before send a message. But in sender.py code right after channel creating you publish a message and if run a sender.py before receiver.py you will not receive

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

Documentation does not include all parameters description for basic_consume API method.
It is also also not documented return values from some methods. Documentation in general look like chaotic and not complete. To get information need constantly to look in library sources.

Channel.basic_consume() now has 2 return values:

• consumer_tag - when nowait == False
• promise object wen nowait == True
• ValueError() when nowait == True and user does not specify consumer_tag

This is confusing since the API is schizophrenic and returns two different values. Moreover promise object does not have any value to user of library.

I propose that consumer_tag is

We're currently having issues with some of our builds that still rely on fairly old versions of akka-rabbitmq

sbt.ResolveException: unresolved dependency: com.thenewmotion.akka#akka-rabbitmq_2.11;2.3: not found

even though we have the resolver configured to use the newmotion Nexus in our build.sbts:

resolvers += "New Motion Repository" at "http://nexus.thenewmotion.com/conten

Description

A new CRD to manage monitoring aspects of EnMasse needs to be defined. The design should cover:

• The schema of the Monitoring CRD
• Cover monitoring of all EnMasse components - including IoT
• Allow for configuring common as well as component-specific aspects
• Cover metric monitoring, alerting and tracing
• Define tasks for backlog

Design

Tasklist

Enu