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, 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