Menu Search

7.3. Broker

The Broker is the principal entity. It is composed of a number of other entities that collaborate to provide message broker facilities.

The Broker can only be managed via the HTTP management channel.

7.3.1. Attributes

  • Name the Broker. This helps distinguish between Brokers in environments that have many.

  • Heartbeating. Enables heartbeats between Broker and Clients. Heartbeats help discover severed TCP/IP connections in a timely manner.

  • Confidential configuration encryption provider. The name of the provider used to encrypt passwords and other secrets within the configuration. See Section 8.4, “Configuration Encryption”.

7.3.2. Context

  • broker.flowToDiskThreshold Controls the flow to disk feature.

  • broker.messageCompressionEnabled Controls the message compression .

  • store.filesystem.maxUsagePercent Maximum percentage of space that may be utilised on a filesystem hosting a virtualhost's message store before producer flow control is automatically imposed.

    This defaults to 90%.

  • qpid.broker_default_supported_protocol_version_reply Used during protocol negotiation. If set, the Broker will offer this AMQP version to a client requesting an AMQP protocol that is not supported by the Broker. If not set, the Broker offers the highest protocol version it supports.

  • qpid.broker_msg_auth If set true, the Broker ensures that the user id of each received message matches the user id of the producing connection. If this check fails, the message is returned to the producer's connection with a 403 (Access Refused) error code.

    This value can be overridden for each Virtual Host by setting the context value on the Virtual Host or Virtual Host Node.

    Defaults to false.

7.3.3. Children

  • Virtualhost nodes

  • Ports

  • Authentication Providers

  • Key Stores / Trust Stores

  • Group Providers

  • Access Control Providers

7.3.4. Lifecycle

Not supported