This is to make this entry complete (and hopefully help someone else avoid spending the time I did trying to solve this). It turns out I needed a commons-logging.properties file in my war's WEB-INF/classes directory. It has a single entry like this:
I need this (I think) because the Unified classloader was picking up a commons-logging.properties file located in ebxmlrr-service.sar\ebxmlrr.war\WEB-INF\classes that looks like this:
I am surprised alot of other people haven't run into this. I was unable to use commons logging in any WAR or SAR that I deploy without overriding the commons-logging.properties file. If I don't do this, my default logger ended up being NoOpLog which eats up all log messages, effectively making everything quiet.
I would think this default behavior should be changed - or otherwise documented somewhere (I could not find the answer to this problem anywhere; maybe I missed it?)
Totally agree with you on documenting this one. Would love to see it in the Wiki.
Thanks - you saved me some time here!
I had this same problem trying to debug jgroups in jboss 4.0.0, which didn't work till I removed the commons-logging.properties from the ebxmlrr folders.
Lot's of thanks - you saved me time here too!