Hi Bryan, Could you please clarify whether you have seen "Gave up waiting" warnings with synchronous or asynchronous recoverer? Do you have full broker log with the warnings? Can you share it? Did you connect consumers to DLQs whilst the VH messages were asynchronously recovered?
Kind Regards, Alex On 19 February 2018 at 14:27, bryand <br...@bldixon.net> wrote: > I was utilizing DLQs (Alternate Binding) for most of my queues and I think > that is why the Virtual Host Node startup time was so slow (1 minute 45 > seconds). After I deleted all those DLQs, the startup time was down to 11 > seconds - a huge difference especially when dealing with a failover > situation. > > Here are some log messages I was seeing in the Broker-j log file regarding > the DLQs (note that all my DLQs were empty): > > 2018-02-12 10:42:24,719 WARN [VirtualHostNode-spgqpiddev3-Config] > (o.a.q.s.m.AbstractConfiguredObject) - Gave up waiting for Queue > 'app_attach_workqueue_DLQ' to attain state. Check object's state via > Management. > > So I'm wondering if there is some type of issue with broker-j regarding > DLQs/Alternate Bindings > > > > > -- > Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
