JMS session, connection, and remoting invokers accumulating in JBoss heap

Solution Verified - Updated -

Issue

  • Our heap usage is slowly and continually growing until an OutOfMemoryError. The heap dump shows accumulation in the following objects:
    • org.jboss.remoting.Client
    • org.jboss.remoting.InvocationRequest
    • org.jboss.remoting.invocation.InternalInvocation
    • org.jboss.jms.server.endpoint.ServerSessionEndpoint
    • org.jboss.jms.server.endpoint.advised.SessionAdvised
    • org.jboss.remoting.ConnectionNotifier
    • org.jboss.jms.server.endpoint.ServerConnectionEndpoint
    • org.jboss.jms.server.endpoint.advised.ConnectionAdvised
    • org.jboss.remoting.InvokerLocator
    • org.jboss.remoting.transport.local.LocalClientInvoker
    • Invokerorg.jboss.remoting.transport.local.LocalServerInvoker

Environment

  • JBoss Enterprise Application Platform (EAP) 5
    • JMS

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.