Since my last post, we have done a number of tests involving some
combinations of the following changes to determine which is more helpful in
alleviating this issue:
1. Increasing the buffer count from 4 to 8;
2. Reducing the receiver capacity from 100 to 10;
3. Upgrading from Windows Server 2003
On 08/29/2013 04:11 PM, Gordon Sim wrote:
On 08/29/2013 03:00 PM, Jakub Scholz wrote:
Right now, it seems that the reconnect(...) method always requires the
URL
of the broker to reconnect to. Maybe it would be useful to also add a
reconnect() method without the URL parameter, to trigger the reco
Hi Gordon,
I raised it as QPID-5106. Thanks for having a look at it.
Thanks & Regards
Jakub
On Fri, Aug 30, 2013 at 12:47 PM, Gordon Sim wrote:
> On 08/30/2013 11:30 AM, Jakub Scholz wrote:
>
>> Hi,
>>
>> The JIRA QPID-4591 added the queue level sequencing. I played with it with
>> the 0.24RC
On 08/30/2013 11:30 AM, Jakub Scholz wrote:
Hi,
The JIRA QPID-4591 added the queue level sequencing. I played with it with
the 0.24RC3 release and it seems it doesn't work properly with AMQP 1.0
producers (C++ / Qpid Messaging API).
My queue is configured with following option:
u'qpid.queu
Hi,
The JIRA QPID-4591 added the queue level sequencing. I played with it with
the 0.24RC3 release and it seems it doesn't work properly with AMQP 1.0
producers (C++ / Qpid Messaging API).
My queue is configured with following option:
u'qpid.queue_msg_sequence': u'queue.sequence'
The connect
Hi Aleš,
I haven't met this, but here are some hints to troubleshoot/investigate it:
1) Before each broker shutdown, run (and keep output of) commands:
qpid-stat -q
qpid-stat -u (to see subscriptions - you will see unacknowledged messages
there)
store_chk (to examine journal content)
2)
