Uploaded image for project: 'ActiveMQ'
  1. ActiveMQ
  2. AMQ-3931

Memory problems with large transactions

    XMLWordPrintableJSON

    Details

    • 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
    • Labels:
      None
    • Environment:

      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.

        Attachments

        1. activemq_log_output.txt
          8 kB
          Robert Voliva
        2. gbsmq.xml
          20 kB
          Robert Voliva

          Activity

            People

            • Assignee:
              davsclaus Claus Ibsen
              Reporter:
              rvoliva Robert Voliva
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: