[AMQ-3931] Memory problems with large transactions

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 5.6.0
• Fix Version/s: 5.7.0
• Component/s: Broker

Environment

OS: RHEL 5.5
Startup options: -Xmx2G -Xms2G -XX:MaxPermSize=512M -Dorg.apache.activemq.UseDedicatedTaskRunner=true -Djava.util.logging.config.file=logging.properties -Dcom.sun.management.jmxremote -Dactivemq.classpath=/opt/activemq/conf; -Dactivemq.home=/opt/activemq -Dactivemq.base=/opt/activemq -Dactivemq.conf=/opt/activemq/conf -Dactivemq.data=/opt/activemq/data -Djava.io.tmpdir=/opt/activemq/tmp
Config file: activemq.xml attached

• Assignee: Claus Ibsen
• Reporter: Robert Voliva
• Created: 16/Jul/12 17:55
• Updated: 19/Sep/12 12:13
• Resolved: 19/Sep/12 12:05

Description

When running a single transaction that produces 300,000 text messages, ActiveMQ runs into all sorts of memory problems. The log output is attached. We were using a simple Java JMS client class to produce the 300,000 messages in a single transaction. Each message's text payload was a random string of 10,000 bytes.

This is a production scenario that we have that's killing our broker. We isolated it down to its most basic pieces to try to test where the breakdown was occuring, which led us to this.