On 02/09/2016 01:09 PM, Toralf Lund wrote:
I can reproduce the problem every time I try now. The other broker is
using the same QPid version, and I think it's supposed to be set up the
same way. It's managed by someone else (who didn't understand the error
message either when I asked), though, so I guess I should check closer.
I don't think anything has changed since it all worked, but I may of
course be missing something (as I tend to suspect when this kind of
thing happens.)
I tried enabling some trace in the broker, too, but didn't notice
anything obvious there, except that the same error message is included a
little section is included below.
I think it is https://issues.apache.org/jira/browse/QPID-5124, which was
fixed from 0.26 (and present in 0.22).
The bug is triggered by sending transient messages to a durable LVQ.
When these messages are displaced by later messages with the same key,
the broker removes them from the queue and - erroneously - tries to
delete them from the store also.
For workarounds, you could either (a) disable the store or make the LVQ
non-durable or (b) send durable messages only to the LVQ .
If you didn't want to do a full upgrade and built from source, you could
just apply the patch or commit associated with the above JIRA.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
