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

Per Destination Memory Usage Limit

    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Resolved
    • Blocker
    • Resolution: Fixed
    • 4.0 M4
    • 4.0 RC2
    • Broker
    • None
    • All

    Description

      Using a global broker memory limit can cause deadlocks. If the memory limit is hit on a broker the send to that broker is blocked. So if I consume a message of the broker and then produce another message on to it that will block cauing a deadlock because I can never consume the message. Having per destination limits will allow me to produce to a different destination with out blocking and messages being consumed from the blocked destination.

      Attachments

        1. ASF.LICENSE.NOT.GRANTED--Queue_Diff
          0.9 kB
          Brian Diesenhaus

        Activity

          People

            Unassigned Unassigned
            bdiesenhaus Brian Diesenhaus
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: