Uses of Package
org.acemq.rabbitmq.admin
Packages that use org.acemq.rabbitmq.admin
-
Classes in org.acemq.rabbitmq.admin used by org.acemq.rabbitmq.adminClassDescriptionLogin attempts one node has counted, for one protocol and — when the broker tracks sources — one remote address and username.A binding: the rule joining an exchange to a queue or to another exchange.One channel on one connection.One client connection, as the broker sees it.One consumer on one queue.Who the broker thinks you are.Everything the broker is configured to be, as one document.A deprecated feature, and how much time is left.An exchange as the broker holds it.One feature flag, and whether it is enabled.A federation link: an upstream and a policy having actually met.Another broker this one may federate from.A cluster-wide parameter, which is not scoped to a virtual host.The broker's own health checks.The answer to one of the broker's own health checks.A limit on a virtual host or a user.One node of the cluster.A runtime parameter: how the broker stores a plugin's configuration.A password hashed the way RabbitMQ's internal user database stores it.What a user may do in a virtual host.A policy: settings applied to whatever matches a pattern.A queue as the broker actually holds it.RabbitMQ's HTTP management API.A shovel: the broker moving messages from one place to another, on its own.One connection over RabbitMQ's stream protocol, on port 5552.One subscription on a stream protocol connection.One publisher on a stream protocol connection.Authorisation for routing keys on a topic exchange.A broker user.A virtual host: the broker's unit of isolation, and the cheapest boundary it offers.