[
https://issues.apache.org/jira/browse/ARTEMIS-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16563781#comment-16563781
]
ASF GitHub Bot commented on ARTEMIS-1999:
-----------------------------------------
Github user michaelandrepearce commented on a diff in the pull request:
https://github.com/apache/activemq-artemis/pull/2203#discussion_r206558769
--- Diff:
artemis-server/src/main/java/org/apache/activemq/artemis/core/server/impl/QueueImpl.java
---
@@ -2370,10 +2370,10 @@ private void deliver() {
}
}
- if (pos == endPos) {
- // Round robin'd all
+ if (pos == endPos || groupConsumer != null) {
--- End diff --
groupConsumer is only set if a msg group is already assigned, or has
succesfully handled. i would change this to check if groupID is not null.
> Broker is using 100% core's CPU time if message grouping is used
> ----------------------------------------------------------------
>
> Key: ARTEMIS-1999
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1999
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 2.6.2
> Reporter: Francesco Nigro
> Assignee: Francesco Nigro
> Priority: Major
> Fix For: 2.6.3
>
> Attachments: cpu.svg
>
>
> When consuming messages with message grouping set on the broker seem to
> consume excessive amount of CPU time. On 12 core CPU it can be observed that
> one core goes 100% and stays that way as long as there is more than one
> consumer attached to a queue. Once the number of consumers is reduced to 1
> the CPU usage goes to normal. But moment another consumer is attached another
> CPU core goes 100%.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
