-
Type:
Bug
-
Status: Done
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: A-MQ 7.0.0.GA, AMQ 7.0.1.GA
-
Fix Version/s: None
-
Component/s: None
-
Labels:
-
Environment:
AMQ 7
QPID AMQP JMS Client
-
Target Release:
-
Steps to Reproduce:
-
Affects:Release Notes
-
Release Notes Text:Previously, persistent messages sent by a AMQ JMS client were not displayed as durable when browsing messages by using the AMQ Console or JMX method call. This issue is resolved in version 7.1.
-
Release Notes Docs Status:Documented as Resolved Issue
Persistent messages sent with QPID AMQP JMS client are not reflected as durable by the broker.
When the persistent messages are browsed via JMX or the Hawtio console the "durable" attribute is set to false. However these messages do persist a broker restart and the queue attribute FirstMessageAsJSON shows the following:
[{"durable":true,"address":"TEST.AMQP","messageID":572924,"expiration":0,"priority":4,"userID":"ID:ID:0cdb9c1a-7fa9-42ef-9cec-a69410258339:1:1:1-2","timestamp":0}]
|
However the durable message attribute is set to false when the messages are browsed.
- relates to
-
ENTMQBR-766 AMQP messages lose durability flag when a conversion happens on broker
-
- Done
-