Uploaded image for project: 'FUSE Message Broker'
  1. FUSE Message Broker
  2. MB-617

Broker hangs during destroy() after getting Out Of Memory when executing NetworkQueueSystemUsage using MeshKeeper


    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s:
    • Fix Version/s: None
    • Component/s: broker
    • Labels:
    • Environment:

      MeshKeeper. NetworkQueueSystemUsage executing from within Eclipse. MeshKeeper control server and launch agent executing on unix (soniclx18). Issue is reproducible when executing against vm-fuseubtXX machines


      A BrokerManager.kill() (Active MQ Broker destroy()) hangs after the broker OOMs.

      To reproduce start a MeshKeeper Control Server and Lauch Agent on a remote host (preferably Linux/Unix). Execute NetworkQueueSystemUsage using the Control Server and Launch Agent. The Broker will hang during the kill():

      13:27:33 [REMOTE] TEST BROKER2: 09:30:14 INFO DemandForwardingBridge: localhost bridge to localhost stopped
      Messages Sent before producer blocked: 25582 (MSGCOUNT is 25583)
      13:27:46 [REMOTE] TEST BROKER1: Exception in thread "ActiveMQ Transport Server Thread Handler: tcp://" java.lang.OutOfMemoryError: Java heap space
      Killing Brokers
      TEST CLIENT: Wire format negotiation timeout: peer did not send his wire format.
      TEST CLIENT: Socket closed
      13:30:47 [REMOTE] TEST BROKER1: Exception in thread "ActiveMQ Scheduler"

      Java thread dump of broker1 attached.

        Gliffy Diagrams




              • Assignee:
                rajdavies Rob Davies
                mpc755 Mike Cavedon
              • Votes:
                0 Vote for this issue
                0 Start watching this issue


                • Created: