[ 
https://issues.apache.org/jira/browse/ARTEMIS-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17201494#comment-17201494
 ] 

Tarek Hammoud commented on ARTEMIS-2859:
----------------------------------------

Hi Gary,

In this case, we did not explicitly use a wild card in the test program and the 
issue seems to manifest in the internal Artemis cluster addresses. How do we 
mark those? Thank you.

> 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: 40m
>  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)

Reply via email to