Dead Message Queue Properties
You configure the dead message queue as you configure other queues,
but certain physical destination properties do not apply or have different
default values. Table 6–3 lists queue
properties that the dead message queue handles in a unique way.
Table 6–3 Dead Message Queue
Treatment of Standard Physical Destination Properties
|
Property
|
Unique Treatment by Dead Message Queue
|
|
limitBehavior
|
The default value for the dead message queue is REMOVE_OLDEST.
(The default value for other queues is REJECT_NEWEST.) Flow control is not supported on the dead message queue.
|
|
localDeliveryPreferred
|
Does not apply to the dead message queue.
|
|
maxNumMsgs
|
The default value for the dead message queue is 1000.
The default value for other queues is -1 (unlimited).
|
|
maxNumProducers
|
Does not apply to the dead message queue.
|
|
maxTotalMsgBytes
|
The default value for the dead message queue is 10 MB. The default value
for other queues is -1 (unlimited).
|
|
isLocalOnly
|
In a broker cluster, a dead message queue is always a global physical destination
and this property is permanently set to false.
|
