The AMQ process stopped on its own after Out of Memory

Solution Unverified - Updated -

Issue

  • Platform Production AMQ failed over from node1 to node1 during production run . NIO transport is being used.
  • We are seeing Out of memory exceptions in system logs of node1.
  • Total Heap is 18 GB but from output of TOP we find 32 GB occupied.
Dec 19 03:45:39 node1 kernel: Out of memory: Kill process 40334 (java) score 934 or sacrifice child
Dec 19 03:45:39 node1 kernel: Killed process 40334, UID 500, (java) total-vm:47844508kB, anon-rss:30804892kB, file-rss:68kB
Dec 19 03:45:52 node1 goferd: [INFO][worker-0] gofer.messaging.adapter.proton.connection:100 - connecting: URL: amqps://node:5647|SSL: ca: /etc/rhsm/ca/some.pem|key: None|certificate: /etc/pki/consumer/bundle.pem|host-validation: None

Environment

  • Red Hat JBoss AMQ
    • 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.