Always assign a dead letter queue (DLQ) to the queue manager.
始终为队列管理器分配死信队列(dead letter queue,DLQ)。
The message is placed in the sending queue manager's Dead Letter Queue.
该消息会放入发送队列管理器的死信队列中。
It is considered a best practice for each queue manager to have a dead letter queue.
我们认为最佳实践是每个队列管理器拥有一个死信队列。
If the message's TTL had already expired at this point, then the message may appear in the sender's Dead Letter Queue.
如果此时消息的TTL已过期，则此消息就会出现发送端的死信队列中。
The total number of bytes that currently reside in the queue. for the computer queues instance this represents the dead letter queue.
当前驻留在队列中的字节总数。对于计算机队列实例，这代表着死信队列。
The total number of messages that currently reside in the queue. for the computer queues instance this represents the dead letter queue.
当前驻留在队列中的消息总数。对于计算机队列实例，这代表着死信队列。
Although an object named SYSTEM.DEAD.LETTER.QUEUE exists, it is necessary to alter the queue manager's DEADQ attribute with the name of the dead letter queue in order to enable it.
尽管存在一个名为SYSTEM . DEAD . LETTER .QUEUE的对象，但要启用死信队列，仍然需要使用死信队列的名称来更改队列管理器的DEAD q属性。
Applications that get messages from the dead-letter queue must verify that the messages begin with an MQDLH structure.
从死信队列获取消息的应用程序必须确保消息以MQDLH结构开头。
Messages can be put on the dead-letter queue by queue managers, message channel agents (MCAs), and applications.
消息可由队列管理器、消息通道、消息通道代理程序(mca)和应用程序放到死信队列上。
This structure includes the name of the destination queue and the reason why the message was put on the dead-letter queue. Table 3 lists the main fields in MQDLH.
该结构包含目标队列的名称和将消息放在死信队列上的原因。
Property indicating the destination queue of the message. Typically used when reading response messages, or messages in machine journals or dead-letter queues.
说明消息目标队列的属性。通常在阅读应答消息，或机器纪录或死信队列中的消息时使用。
In this case, WebSphere MQ adds a dead-letter header structure (MQDLH) to the message, and puts it on the dead-letter (undelivered-message) queue.
在这种情况下，WebSpheremq添加死信头结构(MQDLH)到消息中，并将其放到死信(未传递消息)队列上。
In the case of delivery failure for transactional messages, the message is sent to the transactional dead-letter queue on the source computer in all negative and in-doubt cases.
一旦事务性消息传递失败，则在所有否定的和不确定的情况下，消息将被发送到源计算机上的事务性死信队列。
You do not create a journal or dead-letter queue.
不应创建日记或死信队列。
Because no other indication of message rejection exists, the sending application can lose the message unless you request that it be sent to the dead-letter queue.
因为不存在其他消息遭到拒绝的指示，所以除非您请求将消息发送到死信队列，否则发送应用程序可能丢失该消息。
Messages stored in dead-letter queues count against the size quota for the computer where the queue resides.
存储在死信队列中的消息算在队列所驻留的计算机的大小配额内。
If a message fails delivery, no record of it is maintained in the dead-letter queue.
如果消息传递失败，则不会在死信队列中保留该消息的任何记录。
If a message fails delivery, no record of it is maintained in the dead-letter queue.
如果消息传递失败，则不会在死信队列中保留该消息的任何记录。
应用推荐