DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15195>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15195 AxisServlet logs AxisFault as errors, when it should just be quiet Summary: AxisServlet logs AxisFault as errors, when it should just be quiet Product: Axis Version: 1.0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Basic Architecture AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I have a server that regularly throws exceptions to the client, such as "UserNotFoundException", and they unfortunately end up in the server logs, and in production may end up being sent to the administrator's pager, etc. The severity of a user-defined exception is not really error. The error ends up going to client, anyway, and it doesn't need to be logged in both places. I only am interested in seeing errors that are truly exceptional. I could filter errors out of this one category, but I want to not filter every log message, just one. Suggestion: Log the AxisFault to a different category, such as INFO or DEBUG. Or, create a different catagory for just these errors. File: src/org/apache/axis/transport/http/AxisServlet.java } catch (AxisFault fault) { log.error(Messages.getMessage("axisFault00"), fault); responseMsg = msgContext.getResponseMessage(); if (responseMsg == null) responseMsg = new Message(fault); contentType = responseMsg.getContentType(msgContext.getSOAPConstants()); } Example annoying error message: 2002-12-09 20:02:55,191 ERROR [org.apache.axis.transport.http.AxisServlet] Exception: AxisFault faultCode: {http://xml.apache.org/axis/}Server.userException faultString: com.proteusmobile.dialogserver.DialogServiceNotFoundException: 02003- Unable to find service 1000000000000000000000000002 faultActor: null faultDetail: stackTrace: com.proteusmobile.dialogserver.DialogServiceNotFoundException: 02003- Unable to find service 1000000000000000000000000002 at com.proteusmobile.dialogserver.dialogservice.DBDialogServiceStore.loadService(DBDialogServiceStore.java:376) at com.proteusmobile.dialogserver.webservices.DialogServiceWS.status(DialogServiceWS.java:293) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324)
