By default, calling Session#createConsumer() will cause:

The exchange declare, queue declare and bind side effects can be suppressed using system properties qpid.declare_exchanges, qpid.declare_queues and qpid.bind_queues.

The Client implements each subscription to a Topic as separate queue on the Broker. From the perspective of the JMS application this implementational detail is irrelevant: the application never needs to directly address these queues. However, these details are important when considering Management and Operational concerns.

Durable topic subscriptions use a durable and exclusive queue named as follows:

        clientid: + subscriptionId
      

where subscriptionId is that passed to the Session#createDurableSubscriber(javax.jms.Topic,java.lang.String)

Calling Session#unsubscribe(java.lang.String) deletes the underlying queue.

Non-durable topic subscriptions use a non-durable, exclusive and auto-delete queue named as follows:

        tmp + _ + ip + _ + port + _ + sequence
      

where ip is the ip address of the client with dots replaced by underscores, port is the ephemeral port number assigned to the client's connection, and sequence is a sequence number.

Closing the consumer (or closing the connection) will delete the underlying queue.

With this feature, the Broker keeps track of a number of times a message has been delivered to a consumer. If the count ever exceeds a threshold value, the Broker moves the message to a dead letter queue (DLQ). This is used to prevent poison messages preventing a system's operation. This client feature requires support for the corresponding feature by the Broker.

When using this feature, the application must either set system property qpid.reject.behaviour or the Binding URL option rejectbehaviour to the value server.

See Handling Undeliverable Messages within the Apache Qpid Broker-J book for full details of the functioning of this feature.