Uploaded image for project: 'JBoss A-MQ'
  1. JBoss A-MQ
  2. ENTMQ-1034

Queue Browse message prefetch is being ignored

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • JBoss A-MQ 6.2
    • amqp
    • None
    • Compatibility/Configuration, User Experience
    • Hide

      1) Send to broker 1200 messages via AMQP (check they are really there)
      ./aac1_sender.java.sh --broker amqp://admin:admin@localhost:5672 --address queue_thousands --count 10000

      2) Use QueueBrowser on the same queue with specified queueBrowserPrefetch (=1000)
      ./aac1_receiver.java.sh --log-msgs dict --broker admin:admin@localhost:5672?jms.prefetchPolicy.queueBrowserPrefetch=1000 --address queue_thousands --recv-browse true | wc -l
      400

      We should get an Enumeration of 1000 messages. In my case I always get 400 messages. With or without specified prefetch argument.

      Show
      1) Send to broker 1200 messages via AMQP (check they are really there) ./aac1_sender.java.sh --broker amqp://admin:admin@localhost:5672 --address queue_thousands --count 10000 2) Use QueueBrowser on the same queue with specified queueBrowserPrefetch (=1000) ./aac1_receiver.java.sh --log-msgs dict --broker admin:admin@localhost:5672?jms.prefetchPolicy.queueBrowserPrefetch=1000 --address queue_thousands --recv-browse true | wc -l 400 We should get an Enumeration of 1000 messages. In my case I always get 400 messages. With or without specified prefetch argument.

      The message browsing prefetch does not work properly in AMQP JMS client.
      I always receive 400 messsages (when there is more then 400 msgs in queue), despite the fact, I am using option:
      jms.prefetchPolicy.queueBrowserPrefetch=1000

              Unassigned Unassigned
              mtoth@redhat.com Michal Toth
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: