[
https://issues.apache.org/jira/browse/ARTEMIS-4781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17850171#comment-17850171
]
Justin Bertram commented on ARTEMIS-4781:
-----------------------------------------
The use-case here isn't clear. First you say:
bq. We are producing large AMQP messages...
Then you say:
bq. Note that this also happens for messages that originally were just a few
bytes too small to become a large message, but have become large messages due
to the expiry process.
Are you always producing large message or just sometimes producing large
messages and in the case were you're not producing large messages they become
large due to the expiry process? Please clarify. Thanks!
> on-disk files for large messages are not always removed on expiry
> -----------------------------------------------------------------
>
> Key: ARTEMIS-4781
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4781
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 2.33.0
> Reporter: Erwin Dondorp
> Priority: Major
>
> SETUP:
> Using a broker-cluster.
> The tests are executed with durable and non-durable messages. 3 durable
> messages and 3 non-durable messages are produced every 60 seconds (almost) at
> the same time on the 1st broker.
> We are producing large AMQP messages and leave them on a durable queue.
> MSG/TMP files are created in directory `large-messages` for this as expected.
> After the configured amount of time, the messages expire as expected. the
> original MSG/TMP files are removed as expected.
> For monitoring, we have an simple extra consumer on the address `ExpiryQueue`
> connected to a 2nd broker in the same cluster.
> OBSERVATION:
> The MSG/TMP files are left on the disk of the 2nd broker also every 60
> seconds. This is unexpected. No related logfile lines are seen on either
> broker.
> The content of the MSG/TMP files is (based on it size) related to the
> original MSG/TMP files. These files have different names, likely because they
> have been recreated in the context of the ExpiryQueue address. The files are
> slightly larger, likely because of the addition of a few expiry related
> headers.
> Note that this also happens for messages that originally were just a few
> bytes too small to become a large message, but have become large messages due
> to the expiry process.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
