[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    [jira] [Created] (AMQ-5200) Dispatch of messages within JMSXGroupID is affected by maxPageSize
From:       "Matt Nathan (JIRA)" <jira () apache ! org>
Date:       2014-05-27 8:19:02
Message-ID: JIRA.12716749.1401178724936.21202.1401178742345 () arcas
[Download RAW message or body]

Matt Nathan created AMQ-5200:
--------------------------------

             Summary: Dispatch of messages within JMSXGroupID is affected by \
maxPageSize  Key: AMQ-5200
                 URL: https://issues.apache.org/jira/browse/AMQ-5200
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
    Affects Versions: 5.9.1, 5.9.0, 5.8.0
            Reporter: Matt Nathan


When you have multiple consumers for a single queue and are using JMSXGroupID on each \
message, when one of the consumers is slow the in-memory messages held in the Queue \
in the broker will eventually get filled up with messages that only the slow consumer \
can handle. This means that no other messages are delivered as only the in-memory \
collection is checked for messages awaiting dispatch.

The size of the in-memory collection is controlled by the maxPageSize parameter.

Additionally (and the cause of much confusion in our setup) the expired message \
scheduled task, which runs every 30s by default, will page in more than maxPageSize \
messages, causing additional non-slow messages to be available for dispatch. This \
results in what appeared to be a 30s bursting of messages sent to all non-slow \
consumers.

https://issues.apache.org/jira/browse/AMQ-2217 - the same issue but talks about \
message selectors instead of JMSXGroupID http://stackoverflow.com/q/23810807/317404 - \
my question on StackOverflow



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[prev in list] [next in list] [prev in thread] [next in thread]