Looks like this wasn't a clean shutdown. There were still clients connected
and consuming from the topics and queues. Not sure if that could have
caused the warnings I posted.
After ensuring the client activity had also stopped I was able to do a
clean update without seeing this problem.
Regards,
Is it possible that the index got left behind even though the log files got
deleted?
On Nov 30, 2016 5:25 AM, "Christopher Shannon" <
christopher.l.shan...@gmail.com> wrote:
> Can you post your broker configuration? This seems odd that would happen
> if you removed the db.
>
> On Wed, Nov 30, 20
Can you post your broker configuration? This seems odd that would happen
if you removed the db.
On Wed, Nov 30, 2016 at 5:04 AM, jack patwork wrote:
> Hi,
>
>
> After upgrading a 4 node cluster from 5.9.1 to 5.14.1 I'm seeing my amq
> logs spammed with 1000's of the following warnings. This was
Hi,
After upgrading a 4 node cluster from 5.9.1 to 5.14.1 I'm seeing my amq
logs spammed with 1000's of the following warnings. This was after shutting
down all 4 instances, deleting the db and restarting them.
It looks like the scheduler is stuck in a loop trying to deal with topics
that have b
