David, You are right. I looked into it further, for the OpenEJB.startup category we have three ConsoleAppender instances. For the rest of the categories, there is just one appender.
I have not been able to figure out why this is happening only for the OpenEJB.startup category On 6/26/07, Karan Malhi <[EMAIL PROTECTED]> wrote:
I noticed that too. Initially it did duplicate or triplicate messages because of the parent child relationship you mentioned. That is why i set additivity to false. I was also still getting messages duplicated , but when i looked through the tests, sometimes the log.info calls were made within some code which was looping, hence was logging the same message again and again. Now If you set additivity to false in the doFallbackConfiguration() also, then it might take care of duplicacy for the rest of the loggers. Some of the loggers are also obtained from default.logging.conf. But the conf file does not set additivity to false. So, just bear with this duplicacy a little bit till i fully fix it. On 6/26/07, David Blevins <[EMAIL PROTECTED]> wrote: > With the cumulative.patch on OPENEJB-601, we're getting triple log > messages sometimes. It doesn't happen on all categories. > > I haven't looked, but I wonder if something like this is happening: > > Class Foo asks for "OpenEJB.startup", we add an appender and cache > Class Bar asks for "OpenEJB.startup.validation", we add an appender > and cache > > The end result is that there are two appenders, one on "validation" > directly and on inherited from "startup", and possibly a third > inherited from "OpenEJB" > > But as I say, I haven't looked it just occurred to me based on the > fact that only some log messages repeat and some don't. > > -David > > -- Karan Malhi
-- Karan Malhi
