[
https://issues.apache.org/jira/browse/ARTEMIS-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erwin Dondorp updated ARTEMIS-3125:
-----------------------------------
Description:
This messages appears after sending and manual deleting the first messages to a
fresh installation.
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.
was:
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.
> 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 and manual deleting the first messages to
> a fresh installation.
> 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)
