System queues
The broker uses three system queues. These queues all have names beginning
with SYSTEM.BROKER, and are used for the purposes described below. These queues
are created automatically when the broker starts if they do not already exist.
You might want to alter access authority to these queues.
- SYSTEM.BROKER.CONTROL.QUEUE
- This is the broker's control queue. Publisher and subscriber applications,
and other brokers, send all command messages (except publications and requests
to delete publications) to this queue.
SYSTEM.BROKER.CONTROL.QUEUE is created
as a predefined queue based on the SYSTEM.DEFAULT.LOCAL.QUEUE.
- SYSTEM.BROKER.DEFAULT.STREAM
- This is the queue that receives all publication messages for the default
stream. Applications can also send requests to delete publications on the
default stream to this queue.
SYSTEM.BROKER.DEFAULT.STREAM is created using
SYSTEM.BROKER.MODEL.STREAM if it exists, otherwise the broker predefines it
based on the SYSTEM.DEFAULT.LOCAL.QUEUE.
Note:
SYSTEM.BROKER.DEFAULT.STREAM
is created with a default persistence of yes. This means that an application
using the MQPER_AS_Q_DEF option in the message descriptor (the default) publishes
persistent messages by default.
- SYSTEM.BROKER.ADMIN.STREAM
- This is the queue that the broker uses to publish its own broker configuration
information (for example the identity of its parent). If you write your own
administration applications, they can use the information published on this
stream. You can also publish information on this stream (but not to topics
with names beginning MQ/).
SYSTEM.BROKER.ADMIN.STREAM is created
using SYSTEM.BROKER.MODEL.STREAM if it exists, otherwise the broker predefines
it based on the SYSTEM.DEFAULT.LOCAL.QUEUE.