Paging and large JVM heap usage with low message counts, for AMQ 7 on OpenShift, with ActiveMQ clients
Issue
An AMQ 7 broker on OpenShift reports that paging has started on one or more addresses, with most or all of the JVM heap used by messages. However, the broker console shows a comparatively small number of messages in the broker's backlog. The broker is operated, wholly or partly by OpenWire (ActiveMQ) clients
Environment
- Red Hat AMQ
- 7.1 - 7.9
- Red Hat OpenShift Container Platform
- 4.x
This problem only arises when some of the broker's clients use the ActiveMQ (OpenWire) client runtime libraries.
Later AMQ versions than 7.9 might be affected also, if they result from an upgrade from some earlier version, rather than a fresh installation.
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
