Gordon Sim wrote:
Sounds a lot like https://issues.apache.org/jira/browse/QPID-3352
which is fixed on trunk but just missed out on being included in 0.12
from what I can see. It will be included in 0.14 (alpha packages are
available if you wish to check that it resolves your case:
http://people.apache.org/~jross/qpid-0.14-alpha/).
Thanks Gordon, the Jira description does look very familiar. Funnily
enough RE "if the bridge's AMQP session encounters an error (such as a
queue reaching its maximum capacity upon delivery), messages stop
flowing" one of the reasons that I started looking into queue routes was
so I could have more control of the queue configuration. We'd previously
encountered issues with Dynamic Exchange Routes where a consumer stopped
consuming and the queue filled up and "blew the route" so I wanted more
control of the queue specification (making limit-policy=ring for example)
It would be really nice to have some errors from qpid-route about the
weird
inconsistent state, it's not great that everything *looks* OK when
clearly
it isn't.
Agreed. The issue is that at present the 'bridges' don't track
operational status at all, only the 'links' do. A link corresponds to
the connection (which in this case was fine); the bridge to a session
& subscription (which had failed due to an error).
If you want to raise a JIRA for this hopefully we can get that addressed.
Will do
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
