[
https://issues.apache.org/jira/browse/AXIS2-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926545#comment-17926545
]
Robert Lazarski commented on AXIS2-6065:
----------------------------------------
I decided to change it to debug level since it happens so often.
> Small problem with incorrect log output in AxisServlet#processAxisFault
> -----------------------------------------------------------------------
>
> Key: AXIS2-6065
> URL: https://issues.apache.org/jira/browse/AXIS2-6065
> Project: Axis2
> Issue Type: Bug
> Components: transports
> Affects Versions: 1.8.2
> Reporter: Jeff Thomas
> Priority: Minor
> Fix For: 2.0.0
>
>
> There is a small error in the logged error message within
> AxisServlet#processAxisFault.
> {code:java}
> void processAxisFault(MessageContext msgContext, HttpServletResponse res,
> OutputStream out, AxisFault e) {
> ...
> if (status == null) {
> log.error("processAxisFault() found a null HTTP status
> from the MessageContext instance, setting HttpServletResponse status to: " +
> Constants.HTTP_RESPONSE_STATE);
>
> res.setStatus(HttpServletResponse.SC_INTERNAL_SERVER_ERROR);
> }
> ...{code}
> In the log statement the "HTTP_RESPONSE_STATE" is the name of the
> message-context property ("axis2.http.response.state") - I believe it should
> be the constant HttpServletResponse.SC_INTERNAL_SERVER_ERROR.
> Also, this error actually pops up a lot in our logs... the log.error in both
> the if and the else code generates a lot of spammy output (the logging was
> added with last major version) - suggest maybe considering log-level 'warn'
> instead of 'error'?
> SIDE NOTE: Here in JIRA, Axis 1.8.1 and 1.8.2 are still showing up as
> unreleased versions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
