| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
To match it in unit with the rest of rabbit.
|
| | |
|
| |
|
|
| |
Addressing a TODO of that effect.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Plugins can provide a module to be called to extract extra information
at authentication time. The module name is based on the protocol used. Some
protocols have a space in their name, like "Web MQTT", so spaces in such
cases must be replaced by underscores to come up with a valid Erlang
module name.
[#166271318]
References #1767
|
| |\
| |
| | |
Workaround for IPv6 EPMD
|
| | |
| |
| |
| |
| | |
With this patch it is possible to pass variables to
prelaunch state.
|
| |\ \
| | |
| | | |
Make default worker pool size configurable
|
| |/ /
| |
| |
| | |
Part of rabbitmq/rabbitmq-server#2030.
|
| |\ \
| | |
| | | |
Schema information in mnesia for cli command
|
| | | |
| | |
| | |
| | | |
[#164550205]
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Now, both modules export the same set of functions. This will help with
the backport to `v3.7.x` and thus the life of plugin developers who will
not have to have one copy of their plugin per RabbitMQ version.
|
| | | | |
|
| |\ \ \
| |/ /
|/| | |
Update log configuration tests for rabbitmq/rabbitmq-common#328
|
| |/ / |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Public IPv6 192.240.153.117 is managed by OVH US and has a PTR
117.153.240.192.in-addr.arp record that resolves to www.rabbitmq.com. It
would be nice to move to an IPv4 & IPv6 that are managed by our wider
org.
dig 117.153.240.192.in-addr.arpa PTR +short
www.rabbitmq.com.
whois 192.240.153.117 | grep -i Organiz
Organization: OVH US LLC (OUL-16)
cc @michaelklishin @trevormarshall
|
| |\ \
| | |
| | |
| | |
| | | |
rabbitmq/rabbitmq-server-1767-protocol-specific-ctx-in-authn-authz
Propagate protocol-specific context to authorization
|
| | |\ \
| |/ /
|/| |
| | | |
rabbitmq-server-1767-protocol-specific-ctx-in-authn-authz
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
When one queue confirms a message and another queue failed
without confirming it, the message should be rejected.
Fixes some races between confirms and rejects.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
discard/4 confirms a message, which can cause races between confirms
and rejects.
|
| |\ \ \
| | | |
| | | | |
Add channel info for pending raft commands
|
| | | | |
| | | |
| | | |
| | | | |
[#165184345]
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | | |
'check' function for health check of virtual hosts
|
| | | | | |
| | | | |
| | | | |
| | | | | |
[#163451547]
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Add an option to dead-letter rejected publishes
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Add tests for `reject-publish-dlx` overflow strategy for all corresponding
tests for `reject-publish` strategy. The tests are grouped to avoid code
duplication.
See #1443
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This change splits the tests into groups for both the existing `reject-publish`
overflow strategy and the new `reject-publish-dlx`.
The corresponding queue names have been suffixed to make the tests in the
groups independent and thus parallel.
See #1443
|
| |/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Add `reject-publish-dlx` overflow strategy, which is similar to
`reject-publish` strategy, but also dead-letters rejected messages.
Closes #1443
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The function can be called outside of any AMQP connection (e.g. from the
management plugin), so trying to get any protocol-specific information
from the connection state does not make much sense.
References #1767
|
| | |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Propagate protocol-specific context like MQTT client ID to
authentication and authorization backends. The propagation was already
there for topic authorization. Resource check needed propagation and a
new argument in the backend function. Virtual host check just needed
propagation, as there was already a context parameter (for peer
address).
A context parameter and propagation was already there for login-related
functions.
Unfortunately the context API is not fully consistent, due to historical
reasons: proplists are the historical data structure, maps are used
whenever possible.
References #1767
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add process messages to the error message.
Try harder to kill queues.
|
| | |/ /
|/| |
| | |
| | |
| | | |
This is to prevent false-positives on slow systems and detect genuine
errors better.
|
| |\ \ \
| | | |
| | | | |
Improve quorum_status command
|
| | | | |
| | | |
| | | |
| | | | |
Make it compatible with the pretty table formatter.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
rabbitmq/fix-notify-limiter-after-consumer-timeout-change
Adapt clause in notify_limiter to consumer timeout changes
|
| |/ / / / |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | | |
Make sure that publishes to dead or unaccessible queues return nack
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Channel is counting unacked messages in a remove-only data structure `dtree`.
Each published message id is associated with a list of queues where it was routed to.
On confirm of queue failures queues were removed from the list
As soon as there are no queues in the list - the message can be confirmed.
This meant that if all queues fail with "not abnormal" reasons - the message may be
confirmed, but not enqueued.
This change removes dtree data structure, replacing it with specific unconfirmed_messages
data structure.
It tracks queue pids similarly to dtree, but also has an API to record confirms and failures
differently, keeping track of which queues received at least one confirm.
If all pids fails or confirm, but not all queues received confirmation - it means not all queues
enqueued the message and the message should be rejected
This is different from the current behaviour, but corresponds to the docs and common sense.
[#163952410]
|