Description of problem:
MRG session object does not seem to be able to recover from resource limit exceeded exception.  After the session receives this exception we unable to send any further messages through this session to the broker.

How reproducible:
Easily.

Steps to Reproduce:
Sequence of events:
1) Create a single Exchange,
    a) At this time, there are no active Producers, and no active Consumers
    b) Direct Exchange
2) Start a Consumer that creates its own Queue, and creates a Binding to the existing Exchange
    a) Dynamic Queue (i.e., AutoDelete)
    b) Consumer written in either JAVA or C++
    c) Currently no traffic on the Queue (there are no active Producers)
3) Several Consumers are started
    a) Each Consumer creates its own, separate Queue
    b) Same binding to the same Exchange
4) Start Several Producers
    a) Sending Messages to the Exchange created in Step 1
    b) With the correct Binding Key
    c) Low messge rate, 1 msg every 5 seconds from each Producer
5) The Consumer begins to fall behind, completely filling the Queue
6) Producers begin receiving 'ResourceLimitExceededException'

We understand this is the expected operation, so we attempt to recover...

i) We shutdown the 'offending' Consumer, which deletes the full Queue
    Producers continue to receive the 'ResourceLimitExceededException'
QUESTION: Why does the Producer continue to receive the error message? The error condition has been removed.



Actual results:

Expected results:
The session should recover, meaning we should be able to send messages to the exchange without exceptions being thrown when the error condition has been removed from within the broker.