[jira] Updated: (AMQ-2333) Active MQ performance issues when there are more than 100 queue'd up messages
[ https://issues.apache.org/activemq/browse/AMQ-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Malcom updated AMQ-2333: --- Summary: Active MQ performance issues when there are more than 100 queue'd up messages (was: Active MQ performance issues when there are more than a 100 queue'd up messages) Active MQ performance issues when there are more than 100 queue'd up messages - Key: AMQ-2333 URL: https://issues.apache.org/activemq/browse/AMQ-2333 Project: ActiveMQ Issue Type: Bug Components: Broker, JMS client Affects Versions: 5.2.0 Reporter: Marcus Malcom Over the past couple of days some of our queues get rather full because of downstream problems. The messages start numbering in the 1000's. When that happens ActiveMQ slows way down. I believe is slows down because we are trying to produce a message to the overloaded queue and it's taking a long time (minutes instead of seconds). Once the overloaded queue is emptied the problems go away. Our system pretty much has all the defaults. Note: this was not a problem before upgrading to 5.2.0 Any ideas on what should be done? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-2333) Active MQ performance issues when there are more than 100 queue'd up messages
[ https://issues.apache.org/activemq/browse/AMQ-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Malcom updated AMQ-2333: --- Priority: Critical (was: Major) Active MQ performance issues when there are more than 100 queue'd up messages - Key: AMQ-2333 URL: https://issues.apache.org/activemq/browse/AMQ-2333 Project: ActiveMQ Issue Type: Bug Components: Broker, JMS client Affects Versions: 5.2.0 Reporter: Marcus Malcom Priority: Critical Over the past couple of days some of our queues get rather full because of downstream problems. The messages start numbering in the 1000's. When that happens ActiveMQ slows way down. I believe is slows down because we are trying to produce a message to the overloaded queue and it's taking a long time (minutes instead of seconds). Once the overloaded queue is emptied the problems go away. Our system pretty much has all the defaults. Note: this was not a problem before upgrading to 5.2.0 Any ideas on what should be done? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
