Affects Version/s: 126.96.36.199-fuse
Fix Version/s: None
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
Similar Issues:Show 9 results
MB-1203 Expired msgs not getting acked to broker causing consumer to fill up its prefetch and not getting more msgs. MB-512 Memory leak in JMS Subscriber MB-638 Inner class onMessage method not called when system tests executed on ubuntu machines MB-482 OOM on message consumer and very large memory consumption on broker. MB-1060 Have broker warn on startup if configured to use more memory than is available to the JVM MB-1037 Master and Slave broker instances both shutdown on SQLServer shutdown MB-455 Client consumer hang when using failover transport w/ transactions and jencks pooledConnectionFactory when broker is continually bounced MB-1164 The MirroredQueue feature uses the Topic MemoryUsage instead of the Queue MemoryUsage when forwarding the message to the queue after sending it to the Topic MB-417 Messages are arriving out of sequence using Fuse Message Broker 5.1.
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.