[
https://issues.apache.org/jira/browse/ARTEMIS-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17287116#comment-17287116
]
Gary Tully edited comment on ARTEMIS-3125 at 2/19/21, 3:15 PM:
---------------------------------------------------------------
I am not seeing this, I have the test scenario in one of the integration tests,
but it is not demonstrating the problem. Maybe you can see what is different
between your scenario and this test, and work it into a reproducer.
https://github.com/gtully/activemq-artemis/commit/1e028c175ccd04fd25eed5b756bbc95b37990fa5
was (Author: gtully):
I am not seeing this, I have the test scenario in one of the integration tests,
but it is not demonstrating the problem. Maybe you can see what is different
between your scenario and this test.
https://github.com/gtully/activemq-artemis/commit/1e028c175ccd04fd25eed5b756bbc95b37990fa5
> AMQ222214: Destination X has an inconsistent and negative address size=-6
> -------------------------------------------------------------------------
>
> Key: ARTEMIS-3125
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3125
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.17.0
> Reporter: Erwin Dondorp
> Priority: Major
>
> This messages appears after sending the first messages to a fresh
> installation of 2.17.0.
> AMQ222214: Destination X has an inconsistent and negative address size=-6
> and
> AMQ222215: Global Address Size has negative and inconsistent value as -18
> The reported size grows (in a negative direction) over time. -6, -12, -18 but
> it then seems to stick at -18.
>
> I'm using TTL=60s for the initial message. No expiry queue on ExpiryQueue and
> a min/max expirytime of another 60s on ExpiryQueue to keep the messages there
> for an additional time before finally throwing it away.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
