I thought I'd share that I did finally get everything to work. I share this so that someone in a similar position might be saved some time. Turns out, my config was right all along - the problem was that the classes with the log statements were never being updated, so that effectively, there were no logging calls, hence the empty axis.log file. Once I updated the classes in my web app, everything worked perfectly. -Hugh
The moral of the story, sometimes the problem is totally not wh ----- Original Message ----- > > I borrowed from numerous examples, and use the LogFactory to get a class. > > I've removed the log4j.properties file from the axis.jar and have my own > > which does vary the output. When I set my root category to DEBUG, I can > see > > reams of debug info, just not the debug statements I planted. > > > > Here is the config for log 4j: > > # Set root category priority to INFO and its only appender to CONSOLE. > > > > log4j.rootCategory=INFO, CONSOLE, LOGFILE > > > > # Set the enterprise logger category to FATAL and its only appender to > > CONSOLE. > > log4j.logger.org.apache.axis.enterprise=FATAL, CONSOLE > > # I added these but they don't make any difference. > > log4j.logger.com.gwvas.soap=DEBUG, CONSOLE, LOGFILE > > log4j.logger.system.out=DEBUG, CONSOLE, LOGFILE > > (1) dont replicate the CONSOLE statement or you get double the stuff > (2) hide all the axis debug info with > log4j.logger.org.apache.axis=INFO > >
