Bryan Thanks for reporting the problem. This is a defect in Broker-J 7.0.0 and 7.0.1. The defect will cause startup to be delayed as you have observed (5 seconds (cumulative) per queue or exchange using an alternate binding). The synchronous/asynchronous recoverer and existence or not of consumers has no bearing.
The fix should be straight forward. I anticipate putting it out, as part of a 7.0.2, soon. Keith [1] https://issues.apache.org/jira/browse/QPID-8106 On 20 February 2018 at 14:50, bryand <[email protected]> wrote: > Answers to your questions.. > > Could you please clarify whether you have seen "Gave up waiting" > warnings with synchronous or asynchronous recoverer? > - definitely when using synchronous but also pretty sure it was after I made > the context change to use asynchronous recovery also. I've been making > several changes to get everything cleaned up so I can't remember about > asynchronous for sure. > > Do you have full broker log with the warnings? Can you share it? > qpid.log <http://qpid.2158936.n2.nabble.com/file/t396334/qpid.log> > > Did you connect consumers to DLQs whilst the VH messages were > asynchronously recovered? > - I never had any consumers connected to any of the DLQs > > > > > > > > -- > Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
