JBoss EAP artemis JMS leaks temporary destinations

Solution Verified - Updated -

Issue

  • It would appear that EAP is leaking temporary destinations even though delete() is called on the destination.
  • Suspected memory leak in artemis JMS in JBoss EAP 7.1.3 (no memory leak in EAP 6.4).
  • We migrated our application from EAP 6.4 to EAP 7.1 and it seems memory is leaking in the JMS implementation. After running stress tests for 20h we see more than 100000 instances of org.apache.activemq.artemis.core.paging.impl.PagingStoreImpl which is way more than we expected.

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 7.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content