run for at least 2 hours without the error. But again, some
> QMF based services rely on the updates.
>
>
> Kind regards,
> Pavel Moravec
>
>
> - Original Message -
> > From: "Paul Colby"
> > To: users@qpid.apache.org
> > Sent: Friday, April
ril 13, 2012 11:02:14 AM
> Subject: Re: 0.14 cluster never survives more than an hour or so.
>
> Alas the patch at https://issues.apache.org/jira/browse/QPID-3369
> has not
> fixed the issue.
>
> Interestingly though, it did move the error to a different line, but
> with a
at a time. When more elder nodes
>> are present, all invokes the task on every cluster member, causing more
>> tasks to be executed - that is prevented by broker shutdown.)
>>
>> Kind regards,
>> Pavel Moravec
>>
>>
>> - Original Message -
>> &g
shutdown.)
>
> Kind regards,
> Pavel Moravec
>
>
> - Original Message -
> > From: "Paul Colby"
> > To: users@qpid.apache.org
> > Sent: Thursday, April 12, 2012 5:08:01 AM
> > Subject: 0.14 cluster never survives more than an hour or so.
&
On 04/12/2012 04:08 AM, Paul Colby wrote:
Hi guys,
I'm having an issue with my new 0.14 cluster, where the same configuration
was fine with 0.12.
The cluster starts up, and all brokers are happy. Then, with no client
activity at all, after some seemingly random amount time (usually around 30
m
evented by broker shutdown.)
Kind regards,
Pavel Moravec
- Original Message -
> From: "Paul Colby"
> To: users@qpid.apache.org
> Sent: Thursday, April 12, 2012 5:08:01 AM
> Subject: 0.14 cluster never survives more than an hour or so.
>
> Hi guys,
>
>
Hi guys,
I'm having an issue with my new 0.14 cluster, where the same configuration
was fine with 0.12.
The cluster starts up, and all brokers are happy. Then, with no client
activity at all, after some seemingly random amount time (usually around 30
minutes to an hour) all brokers in the cluste
