Tuning the OpenShift Enterprise v2 messaging service to prevent OutOfMemoryError

Updated -

Symptoms

  • rhc commands such as "rhc app restart" run extremely slowly or time out (HTTP 502 errors from the broker)
  • Commands that invoke MCollective such as oo-stats, oo-mco ping, oo-diagnostics, etc. run very slowly or hang indefinitely
  • Errors in the ActiveMQ logs such as:
| WARN  | Async error occurred: java.lang.OutOfMemoryError: Failed ...

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.