Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-771

Persistent messages sent with QPID AMQP JMS client are not reflected as durable by the broker

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • None
    • A-MQ 7.0.0.GA, AMQ 7.0.1.GA
    • None
    • Release Notes
    • 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.
    • Documented as Resolved Issue
    • Hide

      The AMQP queue shipped with the broker (examples/protocols/amqp/queue) can be used to recreate this issue. The following modification is required to explicitly set the message persistent:

      import javax.jms.DeliveryMode;
...
...
TextMessage msg = session.createTextMessage("Hello world ");
msg.setJMSDeliveryMode(DeliveryMode.PERSISTENT);
sender.send(msg);
      Show
      The AMQP queue shipped with the broker (examples/protocols/amqp/queue) can be used to recreate this issue. The following modification is required to explicitly set the message persistent: import javax.jms.DeliveryMode; ... ... TextMessage msg = session.createTextMessage( "Hello world " ); msg.setJMSDeliveryMode(DeliveryMode.PERSISTENT); sender.send(msg);

    Description

      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.

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-766 AMQP messages lose durability flag when a conversion happens on broker

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rh-ee-ataylor Andy Taylor
              rhn-support-jsherman Jason Sherman
              Petra Svobodova Petra Svobodova (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: