Re: Lock-up in waitForCompletion()

2016-06-01 Thread Toralf Lund
On 01/06/16 10:27, Gordon Sim wrote: 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. Unfor

Re: Lock-up in waitForCompletion()

2016-06-01 Thread Gordon Sim
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 pr

Re: Lock-up in waitForCompletion()

2016-06-01 Thread Toralf Lund
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. H

Re: Lock-up in waitForCompletion()

2016-05-26 Thread Gordon Sim
On 25/05/16 13:53, Toralf Lund wrote: On 24/05/16 16:41, Gordon Sim wrote: On 24/05/16 15:28, Toralf Lund wrote: On 24/05/16 13:22, Gordon Sim wrote: On 24/05/16 12:20, Gordon Sim wrote: if you run: qpid-config queues and: qpid-send -q I think that should allow us to see if there is an

Re: Lock-up in waitForCompletion()

2016-05-25 Thread Toralf Lund
On 24/05/16 16:41, Gordon Sim wrote: On 24/05/16 15:28, Toralf Lund wrote: On 24/05/16 13:22, Gordon Sim wrote: On 24/05/16 12:20, Gordon Sim wrote: if you run: qpid-config queues and: qpid-send -q I think that should allow us to see if there is any queue near its limit. qpid-config

Re: Lock-up in waitForCompletion()

2016-05-24 Thread Gordon Sim
On 24/05/16 15:28, Toralf Lund wrote: On 24/05/16 13:22, Gordon Sim wrote: On 24/05/16 12:20, Gordon Sim wrote: if you run: qpid-config queues and: qpid-send -q I think that should allow us to see if there is any queue near its limit. qpid-config queues says Queue Name Attribute

Re: Lock-up in waitForCompletion()

2016-05-24 Thread Toralf Lund
On 24/05/16 13:22, Gordon Sim wrote: On 24/05/16 12:20, Gordon Sim wrote: On 24/05/16 10:39, Toralf Lund wrote: Hi, I have a program that sends messages to a topic exchange using the C++ messaging API. The messages are generally directed to a single receiver queue. I thought it worked just fin

Re: Lock-up in waitForCompletion()

2016-05-24 Thread Gordon Sim
On 24/05/16 12:20, Gordon Sim wrote: On 24/05/16 10:39, Toralf Lund wrote: Hi, I have a program that sends messages to a topic exchange using the C++ messaging API. The messages are generally directed to a single receiver queue. I thought it worked just fine (as always), but now I notice that i

Re: Lock-up in waitForCompletion()

2016-05-24 Thread Gordon Sim
On 24/05/16 10:39, Toralf Lund wrote: Hi, I have a program that sends messages to a topic exchange using the C++ messaging API. The messages are generally directed to a single receiver queue. I thought it worked just fine (as always), but now I notice that it gets stuck a short while after start

Lock-up in waitForCompletion()

2016-05-24 Thread Toralf Lund
Hi, I have a program that sends messages to a topic exchange using the C++ messaging API. The messages are generally directed to a single receiver queue. I thought it worked just fine (as always), but now I notice that it gets stuck a short while after start-up. Simply put, the sender.send()