qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gordon Sim <g...@redhat.com>
Subject Re: Lock-up in waitForCompletion()
Date Wed, 01 Jun 2016 08:27:44 GMT
On 01/06/16 08:47, Toralf Lund wrote:
> Hi,
>
> I haven't had time to look at this again until now...
>
> I restarted qpidd the on the (current) backup server, and after that, I
> can't reproduce the issue. I guess this means it was indeed related to
> replication. Unfortunately, I never managed to enable protocol trace so
> I could verify it. How is it done, again? (Please excuse my
> forgetfulness.) I tried setting QPID_LOG_ENABLE to "trace:Protocol"
> before starting the process, but it produced no output.

For AMQP 0-10 you need to use trace:Network (or trace+:Network).

> Maybe I might
> have done something on the broker instead, but turning on trace for
> everything didn't seem like a good idea...
>
> Some questions that remain to be answered:
>
> 1. If this was a backup broker issue, why did it affect only one queue?
> 2. Is there any way to configure the broker(s) or queues so that there
>     won't be a complete lock-up like this? I'd rather loose the
>     replication if there is an issue, but I don't really want to disable
>     it altogether, if you know what I'm saying...

Were there any error messages in the logs of either the primary or the 
backups?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Mime
View raw message