On Tue, May 7, 2013 at 7:40 AM, Romain Manni-Bucau <[email protected]>wrote:
> > these logs are important (maybe they should be in debug level) but that's a > geronimo issue if so. Personally if it bothers me i just set the associated > log level to warn (well in prod all logs should be either in war or err). > > Excellent point. thanks. > Did you let the app get enough jms messages to see if it was just a log > you get for each init of the pool or not? > Hmmm, via experience, I learned that the MDBs are pooled, because the Constructor is not executed...always, and with that said, I get these messages every time message is 'sent'. onMessage(), I get these logs. I can and have tolerate(d) these msgs, but I finally improved some task-driven code, and wanted to minimize log a bit, so these lines in the log were on my to-do list. :) I like seeing INFO: ... in my log files, especially, when I'm trying to debug newly-developed code or code that I am monitoring via log files, so I'll tolerate these for now, and may try your recommendation at some point. Thanks Romain!
