[
https://issues.apache.org/jira/browse/ARTEMIS-4576?focusedWorklogId=901030&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-901030
]
ASF GitHub Bot logged work on ARTEMIS-4576:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 22/Jan/24 20:00
Start Date: 22/Jan/24 20:00
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on PR #4749:
URL:
https://github.com/apache/activemq-artemis/pull/4749#issuecomment-1904713729
@howardgao I don't actually understand what's being fixed.. it seems the
same semantic.. replacing 6 by half dozen?
Perhaps you meant to check this for AMQP, in which case you would have to
also check for AMQPLargeServerMessage... or maybe add another method to an
upper level?
if you actually create a test to validate what's wrong, it would be check
the right fix.
Issue Time Tracking
-------------------
Worklog Id: (was: 901030)
Time Spent: 1h 20m (was: 1h 10m)
> ServerSessionImpl#updateProducerMetrics access large messages after being
> routed
> --------------------------------------------------------------------------------
>
> Key: ARTEMIS-4576
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4576
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Howard Gao
> Assignee: Howard Gao
> Priority: Major
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> ServerSessionImpl#updateProducerMetrics method is being called after a
> message is routed. If the message is a large message, it can be acked quickly
> and it's backing file will be closed before the method is being called.
> This bug causes random failure in test
> org.apache.activemq.artemis.tests.integration.paging.MessagesExpiredPagingTest#testSendReceiveCORELarge
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
