Back to bug 1014099

Who When What Removed Added
Martin Svehla 2013-10-01 12:21:20 UTC CC mnovak, msvehla
QA Contact mnovak msvehla
Miroslav Novak 2014-03-06 12:05:36 UTC CC csuconic
Version 6.3.0
Miroslav Novak 2014-03-06 12:08:19 UTC Summary Address settings in default configuration point to non-existent DLQ/expiry queue WARN HQ222180: There are no queues bound into Dead Letter Address jms.queue.DLQ. Messages will ... during start
Jeff Mesnil 2014-03-06 15:34:54 UTC Component JMS HornetQ
Assignee jmesnil csuconic
Jeff Mesnil 2014-03-06 15:39:12 UTC CC jmesnil
John Doyle 2014-03-06 21:28:16 UTC CC jdoyle
Clebert Suconic 2014-03-07 22:11:22 UTC Flags needinfo?(jmesnil)
Jeff Mesnil 2014-03-10 11:30:04 UTC Flags needinfo?(jmesnil)
Jeff Mesnil 2014-03-10 11:31:03 UTC Component HornetQ JMS
Assignee csuconic jmesnil
Link ID JBoss Issue Tracker WFLY-3094
Clebert Suconic 2014-03-10 20:20:32 UTC Blocks 1074682
Clebert Suconic 2014-03-10 20:22:58 UTC Status NEW POST
Clebert Suconic 2014-03-10 20:23:49 UTC Status POST NEW
Jeff Mesnil 2014-03-11 10:14:02 UTC Status NEW POST
Kabir Khan 2014-03-11 16:52:21 UTC Status POST MODIFIED
Target Release --- EAP 6.3.0
CC kkhan
Target Milestone --- DR3
Paul Gier 2014-03-11 21:56:09 UTC Status MODIFIED ON_QA
Miroslav Novak 2014-03-13 10:07:57 UTC Status ON_QA ASSIGNED
Miroslav Novak 2014-03-13 10:31:17 UTC Status ASSIGNED VERIFIED
John Doyle 2014-03-13 15:35:34 UTC CC jdoyle
Jeff Mesnil 2014-06-03 06:57:45 UTC Doc Text Feature:

The messaging subsystem configuration now includes two JMS queues
for the dead letter queue and the expiry queue.

Reason:

The default address settings was configured to send expired messages to an expiry address and undelivered messages to a dead letter address. However there were no queues bound to theses address and it resulted in message loss preventing administrators to examine these messages and diagnostic potential application issues.

Result (if any):

Expired messages will now be stored in the DLQ queue and undelivered messages will now be stored in the ExpiryQueue.
Doc Type Bug Fix Enhancement
Scott Mumford 2014-06-05 04:04:50 UTC CC smumford
Doc Text Feature:

The messaging subsystem configuration now includes two JMS queues
for the dead letter queue and the expiry queue.

Reason:

The default address settings was configured to send expired messages to an expiry address and undelivered messages to a dead letter address. However there were no queues bound to theses address and it resulted in message loss preventing administrators to examine these messages and diagnostic potential application issues.

Result (if any):

Expired messages will now be stored in the DLQ queue and undelivered messages will now be stored in the ExpiryQueue.
This release of JBoss EAP 6 includes an enhancement to the messaging subsystem configuration which now includes two JMS queues for the dead letter queue and the expiry queue.

In older releases the default address settings were configured to send expired messages to an expiry address and undelivered messages to a dead letter address. However there were no queues bound to theses address and it resulted in message loss preventing administrators to examine these messages and diagnostic potential application issues.

Expired messages will now be stored in the DLQ queue and undelivered messages will now be stored in the ExpiryQueue.
mark yarborough 2014-06-28 15:26:43 UTC Status VERIFIED CLOSED
Resolution --- CURRENTRELEASE
Last Closed 2014-06-28 11:26:43 UTC

Back to bug 1014099