Hi Gordon, IMHO it would be great if they can be moved to a lower log level. I think it is not a correct behaviour when you have warning messages, but they are nothing to worry about.
Regards Jakub On Wed, Sep 7, 2011 at 12:15, Gordon Sim <[email protected]> wrote: > On 09/06/2011 06:21 PM, Alex Kulyavtsev wrote: >> >> Shall we worry about this type of warnings in the log? Is there way to >> suppress these messages and/or increase threshold for "late" reports? > > I don't think you need to worry about them. The only reason for being > concerned with the exact timings of scheduled or reoccuring events that I > can see is if you are getting clients timed out by the broker even though > they are active (heartbeating in the broker shares a timer with these other > tasks). > > I personally think those log statements are at the wrong level. Since they > are warnings it is not easy to turn them off without missing other more > useful messages. The only way you can do so is to set the default level to > error and then enable notice+ for every other log category (which is not > easy to determine). > > I'll make the argument for getting this changed... > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > > --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
