HornetQ memory leak when undefined destination is used

Solution Verified - Updated -

Issue

  • We have an MDB deployed that we're not using. The MDB is looking for a destination that isn't defined. This appears to be causing a memory leak. We saw 600-800 HornetQ threads spawned resulting in an OutOfMemoryError. Since the destination was added, the thread count has been stable.

Environment

  • Red Hat JBoss Enterprise Application Platform
    • 6.1.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

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