This week's book giveaway is in the Programmer Certification forum. We're giving away four copies of OCP Oracle Certified Professional Java SE 11 Programmer I Study Guide: Exam 1Z0-815 and have Jeanne Boyarsky & Scott Selikoff on-line! See this thread for details.
My new question is about *how* it should work, I'm 99% sure that this is how its supposed to work but I just want some confirmation.
I do have log4j working and logging to its own file, I will eventually customise this further.
My question is, WebSphere acts quite differently to Tomcat in regard to log4j logging, as in the use of ConsoleAppender does absolutely nothing in WebSphere. WebSphere's JDK logging appears to still run for the SystemOut file, and it can be customised through the WebSphere interface. AND the log4j logging also works to a file perfectly fine.
So my question is, is this the way log4j works through WebSphere?
We're logging to the commons-logging interface with log4j as an implementer but this application appears to log to both log4j (and the file specified in the properties) AND the JDK logger that WebSphere normally uses.
This is a good feature for us but I would like to confirm that we haven't done anything wrong here?
Provided an answer eventually. It would appear controlling WebSphere's SystemOut with Log4j is not possible, I consider this a good feature as you get log4j logs + the dynamic control over WebSphere's logging.