Menu Search

Appendix B. System Properties

The following table describes the Java system properties used by the Broker to control various optional behaviours.

The preferred method of enabling these system properties is using the QPID_OPTS environment variable described in the previous section.

Table B.1. System properties

System propertyDefaultPurpose
qpid.broker_heartbeat_timeout_factor2Factor to determine the maximum length of that may elapse between heartbeats being received from the peer before a connection is deemed to have been broken.
qpid.broker_dead_letter_exchange_suffix_DLEUsed with the Section 9.4.3, “Dead Letter Queues (DLQ)” feature. Governs the suffix used when generating a name for a Dead Letter Exchange.
qpid.broker_dead_letter_queue_suffix_DLQUsed with the Section 9.4.3, “Dead Letter Queues (DLQ)” feature. Governs the suffix used when generating a name for a Dead Letter Queue.

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 is check is currently not enforced when using AMQP 0-10 and 1-0 protocols.


If set true, the Broker will produce operational logging messages.


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.


Allows optional Broker features to be disabled. Currently understood feature names are: qpid.jms-selector

Feature names should be comma separated.


Maximum AMQP frame size supported by the Broker.


Used when using ACLs and the JMX management interface.

If set true, the METHOD object permission is sufficient to allow the user to perform the operation. If set false, the user will require both the METHOD object permission and the underlying object permission too (for instance QUEUE object permission if performing management operations on a queue). If the user is not granted both permissions, the operation will be denied.


Applicable to the JMX management interface. If true, the Broker creates a custom RMI socket factory that is secured from changes outside of the JVM. If false, a standard RMI socket factory is used.

It is not recommended to change this property from its default value.


Controls the number of recent Broker log entries that remain viewable online via the HTTP Management interface.