Per Destination Memory Usage Limit

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.