Dumitru HUSLEAG created AMQ-6062:
------------------------------------
Summary: Broker goes 100% CPU on multi-queue command line browse
Key: AMQ-6062
URL: https://issues.apache.org/jira/browse/AMQ-6062
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.12.0, 5.9.1
Environment: Linux Ubuntu, Aix, with both Java 6 and Java 7
Reporter: Dumitru HUSLEAG
Priority: Critical
Hello,
The case happend in a production environment forcing us to kill the broker and
restart because he was nor responding anymore to clients.
The Broker may enter a state of high CPU consumption (100% or 200% if 2 browse
enter the infinite loop in the same time). Tested version: 5.9.1 and the last,
5.12.0, but of course I suppose all in beetwen are affected.
The scenario may be produced with a fresh non modified install (and config) of
ActiveMQ broker:
1. set ACTIVEMQ_HOME, JAVA_HOME and PATH to point accordingly to the right
activemq, and Java version.
2. cd $ACTIVEMQ_HOME/bin; ./activemq start
3. inject at least 2000 messages in each of two ques, say QA.ONE and QA.TWO
4. $ $ACTIVEMQ_HOME/bin/activemq browse --view JMSDestination,JMSMessageID
--amqurl tcp://localhost:61616 QA.*
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
