----- Original Message ----- From: "Richard Sitze" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, October 22, 2002 4:11 PM Subject: Re: DO NOT REPLY [Bug 13845] - Axis logs/prints and exception when it shouldn't
> (bugzilla down...) Ok, I thought it was me, our network is playing up today. with 1 ping in 3 to my mailserver dropping out. > > Don't forget about our "enterprise" level logging. It's not clear to me > that this particular situation applies.. but it's out there if it does. We need to look at logging in general. I've just been tweaking the AxisServlet so that when the development property is set (axis.development.system) , then we do return a stack trace on invalid WSDL, but even that isnt enough to help me track down why the WSDL is broken. So in this case we need more diagnostics, not less. The big issues we have with exceptions right now are 1. we dont distinguish between 'valid' exceptions from the invocation, and unexpected faults, hence the bugrep. 2. the body of axis faults created by wrapping other exceptions, often contains stack traces that we dont want to get out to the caller. Really we need to -keep stack trace info separate and private at production time -distinguish endpoint originated exceptions from other exceptions, and not log the endpoint ones How can we go about doing this?
