On Wed, 28 Nov 2001, Leo Sutic wrote: > Giacomo, > > it is important, but only when you are tuning pool sizes. Otherwise each > request will result in 10-20 log entries from the pool, which will drown out > more important information. > > I'd prefer a note in the docs: Set log-level to DEBUG when tuning pool > sizes.
Well, this is exactly what I'd like to go round :). This way the pool tuning information will get lost in all the other debugging information an application like Cocoon is producing :/. The approach Peter is proposing (a dedicated logging category) seems to be a way to go to handle that specific use case. But than we'll have a hardcoded category in the pooling system. Is that ok? Giacomo > > /LS > > > -----Original Message----- > > From: giacomo [mailto:[EMAIL PROTECTED] > > > > I'd like to raise some of the logging messages from DEBUG to INFO for the > > poolable objects in the ExcaliburCM system because decommissioning of > > objects is an important pool tuning information and IMO they should have a > > higher logging level as they have today. > > > > Any objections? > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
