log4j.logger.org.apache.axis.EXCEPTIONS=WARN log4j.logger .org.apache.axis.enterprise=WARN
you can try it and see if it helps or maybe in your case exceptions go into some other loggers too.
Or as an alternative you can try to Threshold some of the appenders.
if you provide you own exception class derived from AxisFault then you can use it when you throw your own exception but when Axis creates exceptions it will still continue to use AxisFault.
oleg
Josh Emmons wrote:
I'm being overwhelmed by the huge stack traces that are put into the "faultDetail" field of AxisFault by default. My log file is 10x the size it should be with all those stack traces taking up space. Is there something I can put in my log4j.properties file to exclude this junk?
There was a reply on the list not so long ago that suggested subclassing AxisFault and throwing that instead of a normal exception. I've tried that, but can't figure out how to get rid of the faultDetails. I've tried putting "setFaultDetail(null);" and "setFaultDetailString("");" in the subclass's constructor, but that didn't seem to make any difference at all. The API docs on these methods are all but silent. Can anyone point me in the right direction, or will I just have to learn to put up with overly-verbose stack traces?
Cheers, -Josh Emmons
