Uploaded image for project: 'ActiveMQ Artemis'
  1. ActiveMQ Artemis
  2. ARTEMIS-2188

Paged large message results in pagingStore sizeInBytes leak when the page is evicted

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.6.4, 2.7.0
    • Component/s: Broker
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              wy96f yangwei
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 10m
                10m