[ARTEMIS-2859] Strange Address Sizes on clustered topics.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.12.0, 2.14.0
• Fix Version/s: 2.16.0
• Component/s: Broker

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)

• Assignee: Gary Tully
• Reporter: Tarek Hammoud
• Created: 29/Jul/20 18:06
• Updated: 03/Nov/20 01:17
• Resolved: 15/Oct/20 08:14

Description

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.javabroker.xml

Issue Links

• fixes: ARTEMIS-2768 Negative AddressSize in JMX
• fixes: ARTEMIS-2888 MQTT spec violation when subscribed to wildcard topic
• links to: GitHub Pull Request #3238
• links to: GitHub Pull Request #3282