Description of problem:
The QMF agent effectively ignores queue resource exhaustion events. Currently, the agent will immediately reconnect and continue publishing data when a queue exhaustion exception occurs. This behavior exacerbates the queue saturation problem by creating additional unsolicited management messages (binding, etc).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. See https://bugzilla.redhat.com/show_bug.cgi?id=615441
The QMF agent immediately re-connects and continues publishing object status messages.
The agent should handle the exception more gracefully by backing off the reconnection attempt, and further by delaying the next object update cycle/throttle back the number of objects published.
Created attachment 438490 [details]
Backoff reconnect attempt if connection dropped due to queue limit violation.
I've tried the above patch in testing in my high traffic/slow consumer setup - there was no noticible improvement to performance when simply backing off the reconnect attempt. Including patch for reference - not submitting it as a fix.