[
https://issues.apache.org/jira/browse/ARTEMIS-2859?focusedWorklogId=492929&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-492929
]
ASF GitHub Bot logged work on ARTEMIS-2859:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 30/Sep/20 12:41
Start Date: 30/Sep/20 12:41
Worklog Time Spent: 10m
Work Description: gtully commented on pull request #3282:
URL: https://github.com/apache/activemq-artemis/pull/3282#issuecomment-701364383
This seems quite a big change but I think it is the root cause. I see that
routing to the remote binding can attempt to page the message to the cluster
connection queue store, which competes with the local queue binding paging to
the target address, the topic address. This seems wrong.
Having the remote binding just add the store and forward queue to the topic
binding, rather than an entry in the routing context bindings map for the
store and forward address, avoids the contention. It seems wrong that it would
page to the store and forward queue address!
Lets hope some existing test can show me the error if this logic is flawed.
The new test that verifies the non negative size of the page store for the
topic works as expected with this fix.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 492929)
Time Spent: 1h 20m (was: 1h 10m)
> Strange Address Sizes on clustered topics.
> ------------------------------------------
>
> Key: ARTEMIS-2859
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2859
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.12.0, 2.14.0
> Environment: uname -a
> Linux tarek02 4.4.0-78-generic #99-Ubuntu SMP Thu Apr 27 15:29:09 UTC 2017
> x86_64 x86_64 x86_64 GNU/Linux
> java version "1.8.0_251"
> Java(TM) SE Runtime Environment (build 1.8.0_251-b08)
> Java HotSpot(TM) 64-Bit Server VM (build 25.251-b08, mixed mode)
> Reporter: Tarek Hammoud
> Assignee: Gary Tully
> Priority: Major
> Fix For: 2.16.0
>
> Attachments: TestClusteredTopic.java, broker.xml,
> image-2020-08-03-14-05-54-676.png, image-2020-08-03-14-05-54-720.png,
> screenshot.png
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> !screenshot.png! Hello,
> We are seeing some strange AddressSizes in JMX for simple clustered topics.
> The problem was observed on 2.12.0 in production but can also be reproduced
> on 2.14.0. I set up a 3-node cluster (Sample broker.xml) attached. The test
> program creates multiple clustered topic consumers. A publisher sends a
> message every few seconds. The JMX console shows a strange address size on
> one of the nodes. Easy to reproduce with the attached test program. Seems to
> be fine with queues.
> Thank you for help in advance.[^TestClusteredTopic.java][^broker.xml]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
