Details
-
Bug
-
Resolution: Done
-
Minor
-
None
-
AMQ 7.6.0.GA
-
None
-
User Experience
Description
PageCurosrProviderImpl::cleanup is calling PageCurosrProviderImpl::finishCleanup that's fully reading pages (when not present in the PageCache), just to trigger large messages delete.
The decoding phase could be skipped and possibly the page read as well.
Although marked as bug, this issue can be seen as an improvement too, but anyway it affects user esperience with the broker.
The issue happens if the broker has a huge backlog of not consumed pages (> page-max-cache-size) and could lead to OOM depending on how the heap size is being configured and the current memory occupation while consuming the backlog.