JBoss runaway memory on startup

Solution Unverified - Updated -

Issue

  • Sometimes (not always) the memory usage keeps increasing during the deployment (startup) phase.

  • The JBoss process takes as much memory as possible until the machine stalls.

  • There is no associated exception or error message.

  • When Jboss starts without memory problems, all the applications are running and stable and consuming around 1.3GB.

  • When Jboss server starts with memory issues, it uses more then 5GB.

  • Memory is always out of control when there is an exception during the deployment of one of the ESB applications. For example, when there is already an MBean queue registered (because it failed to undeploy when stopping the server), then an exception is thrown during the deployment phase. When this happens, we always see huge memory usage (>5GB).

Environment

  • JBoss Service Oriented Architecture Platform (SOA-P) 4.3 CP02

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