I guess its handy during development to have elevated log levels:-



Perhaps this development is far enough along to not require this now ?

Perhaps those really should just be DEBUG level messages. I'll go back and reconsider all that b4 calling this stuff *done*. Not sure though. My definition of INFO is "interesting event", for which I think binding/unbinding, session-creation/close still qualify.

I think the default log level in jboss for its internal stuff is INFO for the log-file and WARN for the console. Is that not correct?

Not precisely. from log4j.xml:


Binding/unbinding stuff seems very routine and not interesting (since it works properly ;)

I'd also vote for DEBUG.

Its debug. Specifically its debug because of the sheer volume of them. Info is used for deployments/undeployments as they are the interesting events. Every EJB invocation is hopefully uninteresting.

Possibly some of the logging could use the trace level used within JBoss. Also, all the debug/trace logging should be updated to use the isDebugEnabled as per standard practice.

isDebugEnabled is really only used/needed if the message to be logged is expensive to generate; the pivot being the expense of performing the isDebugEnabled check vs the message construction. Most of these messages are simple string logging.

Anyway, like I said before, when this is all complete I will go back and evaluate the logging.