Uploaded image for project: 'A-MQ Broker'
  1. A-MQ Broker
  2. ENTMQBR-475

address-full-policy="DROP" is not respected with non-persistent messaging

    Details

    • Type: Bug
    • Status: Done
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: A-MQ 7.0.0.ER12
    • Fix Version/s: A-MQ 7.0.0.ER14
    • Component/s: None
    • Labels:
      None
    • Environment:

      JBoss A-MQ beta

    • Target Release:
    • Steps to Reproduce:
      Hide

      1. Create an A-MQ broker and set

      <address-setting ... address-full-policy="DROP" max-size-bytes="1000000" .../>
      

      along with

      <server name="default" persistence-enabled="false">
      

      Using any test client, post messages until the total payload is greater than 1Mb. Note that all the messages are accepted.

      2. Enable persistence, and repeat test. Note that messages are ignored (without error) once the total sent is greater than ~1Mb, as expected.

      3. Disable persistence, and set

      address-full-policy="DROP"
      

      Note that clients are blocked, as expected, once the total payload gets to 1Mb. It seems that it is only the combination of DROP and non-persistent messaging that does not work.

      Show
      1. Create an A-MQ broker and set <address-setting ... address-full-policy= "DROP" max-size-bytes= "1000000" .../> along with <server name= " default " persistence-enabled= " false " > Using any test client, post messages until the total payload is greater than 1Mb. Note that all the messages are accepted. 2. Enable persistence, and repeat test. Note that messages are ignored (without error) once the total sent is greater than ~1Mb, as expected. 3. Disable persistence, and set address-full-policy= "DROP" Note that clients are blocked, as expected, once the total payload gets to 1Mb. It seems that it is only the combination of DROP and non-persistent messaging that does not work.

      Description

      When setting a maximum message capacity on a destination, with address-full-policy=DROP, the policy is not respected when persistence is disabled. This might be an unavoidable consequence of disabling persistence, but the BLOCK policy is respected.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  ataylor Andy Taylor
                  Reporter:
                  kboone Kevin Boone
                  Tester:
                  Petra Svobodova
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  8 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: