Menu
▾
▴
#80 log4j logging in pool and connector
I finished converting the pool and connector modules to
log4j logging, and reformatted the code to guidelines.
My strategy for dealing with the "PrintWriter for
logging" issue in the connector api is:
All jboss supplied classes actually use log4j for
logging. If they have a setLogWriter method, the value
is ignored.
If jboss is setting up an object with an api-required
setLogWriter method, it is called with a
logging.log4j.CategoryWriter, writing to a category
based on the class of the configured object.
The only place this applies at the moment is
ConnectionFactoryLoader. ConnectionManager also has a
setLogWriter method, but each ConnectionManager has its
own ConnectionManagerFactory, so if someone provides a
different ConnectionManager they can provide a specific
ConnectionManagerFactory that appropriately configures
logging.
david jencks
Logged In: YES
user_id=60525
I should also mention that since ConnectionManager logging
is now through log4j I removed the properties that
controlled "pool" logging through jcml configuration.