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

destination header replaced for wildcard address during paging

    XMLWordPrintable

Details

    • False
    • False
    • Hide
      Cause-Consequence-Fix-Result ?
      The address field was being set on a message before it was stored to reflect the page store name. This was incorrect if the page store was for a wildcard subscriber.

      The consequence was an incorrect destination name header when the message was read from the store if it had been paged first for a wildcard subscriber.

      The fix is not to change the message content when the message is written to the page store, leaving the original target address.

      The result is that the message destination header is now intact after paging.
      Show
      Cause-Consequence-Fix-Result ? The address field was being set on a message before it was stored to reflect the page store name. This was incorrect if the page store was for a wildcard subscriber. The consequence was an incorrect destination name header when the message was read from the store if it had been paged first for a wildcard subscriber. The fix is not to change the message content when the message is written to the page store, leaving the original target address. The result is that the message destination header is now intact after paging.
    • Verified in a release

    Description

      If a consumer subscribes to a wildcard address `test.*.A` a new address is auto-created `test.*.A` when the consumer connects. 

      This causes a problem because messages published to 'test.foo.A' will be sent to the `test.*.A` address rather than `test.foo.A`.  When paging is started on the destination, the message 'destination' header is now `test.*.A` in stead of `test.foo.A`.  If consumers rely on the 'destination' header for processing, the original destination is lost.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-4427 [LTS] destination header replaced for wildcard address during paging

          • 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
          relates to

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-3875 Inconsistent and negative address size

          • 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

              gtully@redhat.com Gary Tully
              rhn-support-shiggs Stephen Higgs
              Oleg Sushchenko Oleg Sushchenko
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: