Large number of Hornetq PagePositionImpl instances in memory

Solution Verified - Updated -

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.1.0
    • 6.2.0
    • 6.3.0

Issue

  • With paging turned on, a large number of PagePositionImpl instances accumulate in memory, and do not go away until garbage collection kicks in.
  • We're going through and upgrade at the moment for an application running in Jboss EAP 6.2. They hit an issue where the vendor recommended patching (referring to
    https://access.redhat.com/solutions/1210273) Can you advise where that patch is?
  • we have been recommended by our vendor to download the latest patch for the issue related to HORNET-Q paging ((https://access.redhat.com/solutions/1210273),
    We are currently running on jboss 6.2 EAP. Is this patch compatible with 6.2? Could you please provide the instructions to install this patch and how can we verify if we have the patch
    correctly installed.

Resolution

This is a known issue reported in BZ#1141873.

It is fixed in EAP 6.3.3 and EAP 6.4.0 or later, which you can download from the customer portal:

Root Cause

There is an issue where PagePositionImpl are not being cleared in one specific scenario.

The PagePosition is held for every acked paged message until the entire page has been acked for a specific cursor or a subscription.

After the entire page is cleared ackedPositions are cleared and removed positions should also be cleared and replaced by a single instance that is held for the entire file. This was not happening so the positions were growing more than expected.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.