I'm all too familiar with this error. At least for me, it was my java client code. What happen was that the consumer subscription service was ack on the wrong channel. You must be sure that each consumer subscription is on its own thread and that your source code is not being overridden from another subscription initalization. For me, whatever was the last consumer subscription service being register was being use by all.
On Thu, Mar 6, 2014 at 9:47 AM, Simon MacMullen <[hidden email]> wrote:
On 06/03/14 14:45, Patrick Long wrote:
Are there other reasons for seeing this error ?
By far the most common reason for this error is acking the same message twice.