[jira] [Closed] (ARTEMIS-2188) Paged large message results in pagingStore sizeInBytes leak when the page is evicted

["clebert suconic (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARTEMIS-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

clebert suconic closed ARTEMIS-2188.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.6.4
                   2.7.0

> Paged large message results in pagingStore sizeInBytes leak when the page is evicted
> ------------------------------------------------------------------------------------
>
>                 Key: ARTEMIS-2188
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2188
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>            Reporter: yangwei
>            Priority: Major
>             Fix For: 2.7.0, 2.6.4
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> When we write a paged large message, addLiveMessage->incrementDelayDeletionCount->
> incrementRefCount->onDurableUp is called where pagingstore size and global size is added.
> The page where the large message resides maybe evicted from cache.
> When the page is deleted, LargeServerMessageImpl::decrementDelayDeletionCount is called the last time but the large message is not the original one which means context is null and nonDurableDown is not called resulting in pagingstore size and global size not properly subtracted.
> Writing large paged message should be handled like regular paged message. The large paged message doesn't account for the memory size, we don't need to call PagingStoreImpl::onDurableUp.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)