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

Clarify reserved characters in AMQ 7

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Critical
    • None
    • A-MQ 7.0.0.GA
    • None
    • Documentation (Ref Guide, User Guide, etc.), Release Notes
    • Hide
      In prior releases, in was unclear which characters should not be used when creating destination names, addresses, client IDs, and other configuration elements. This information was added to the product documentation titled Using AMQ Broker under the section "Address and Queue Naming Requirements" (https://access.redhat.com/documentation/en-us/red_hat_jboss_amq/7.1/html-single/using_amq_broker/).
      Show
      In prior releases, in was unclear which characters should not be used when creating destination names, addresses, client IDs, and other configuration elements. This information was added to the product documentation titled Using AMQ Broker under the section "Address and Queue Naming Requirements" ( https://access.redhat.com/documentation/en-us/red_hat_jboss_amq/7.1/html-single/using_amq_broker/ ).
    • Documented as Resolved Issue
    • AMQ Broker 7.1 Sprint 2

    Description

      Please document what characters are reserved in AMQ 7 and that should not be used in destination names, addresses, client ids, subscription names, etc across different clients like JMS core, native core, openwire, AMQP.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. AMQDOC-2609 Customer feedback: Document what characters are safe to be used as separator in AMQ 7 across protocols and APIs

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-897 Openwire client/protocol issues with special characters in destination name

          • 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-718 Can't use / or _ in queue names

          • 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

          Bug - A problem that impairs or prevents the functions of the product. ENTMQBR-900 Hawtio weirdly divides address name and queue name containing minus and/or comma

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              mtoth@redhat.com Michal Toth
              rhn-support-tmielke Torsten Mielke
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: