The latest release of RFA Java that supports the Market Data programming interface (SSL connection) is RFA Java 7.6.1.L1 release. However this would require the upgrade of Java version as well since RFA Java 7.4 or higher requires Java 7.

From the given heap screen snapshot, large amount of memory was retained by EventQueue object, which basically holds data events received from the infrastructure. This indicates the possibility that a lot of data events were pending (for processing) in the event queue and the application was likely experiencing the slow consumer condition - the application did not process events fast enough.

Generally, there are two main approaches to address the slow consumer problem, i.e. a) improving the event processing capability of the application, and b) reducing the number of updates (by applying update conflation).

To improve the event processing, the developer could review and optimize the event processing routine so that less time is spent on processing events. The application can also be revised to have multiple sessions and connections (having more threads) to distribute the workload across different CPU cores.

On the other hand, if the application cannot be changed, performing the update conflation (on the infrastructure) should be considered. This would reduce the number of updates the application has to handle; however, at the expense of not having all ticks of updates.

Please see the following answer investigating RFA memory growth. Rising data rates with slow consumers, either by hardware limits or by complex processing will see additional buffer consumption and eventual memory exhaustion.

It is recommended to investigate enabling just-in-time conflation in TREP to reduce the data rates being presented to the consuming application during peak trading hours.

Note that RFA/Java 5.x, 6.x, 7.0, and 7.2 are no longer supported, similarly JRE versions 4, 5, and 6. Code changes will be required to upgrade, and it may be easier to migrate to the new Elektron SDK (EMA) instead.