Affects Version/s: 220.127.116.11-fuse
Fix Version/s: None
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://0.0.0.0:61616" java.lang.OutOfMemoryError: Java heap space
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.