[ https://issues.apache.org/jira/browse/AXIS2-6086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Lazarski resolved AXIS2-6086. ------------------------------------ Resolution: Fixed Thanks for letting us know. I added some Exception handling, and I added some comments so that these logging levels changes don't happen again. > AxisServlet - processAxisFault - does not guard against NumberFormatException > ----------------------------------------------------------------------------- > > Key: AXIS2-6086 > URL: https://issues.apache.org/jira/browse/AXIS2-6086 > Project: Axis2 > Issue Type: Bug > Components: transports > Affects Versions: 2.0.0 > Reporter: Jeff Thomas > Priority: Minor > Fix For: 2.0.1 > > > In the {{AxisServle#processAxisFault}} there is an unguarded > {{Integer.parseInt}} which could propagate a {{{}NumberFormatException{}}}. > {code:java} > if (status == null) { > log.error("processAxisFault() on error message: " + e.getMessage() + " , > found a null HTTP status from the MessageContext instance, setting > HttpServletResponse status to HttpServletResponse.SC_INTERNAL_SERVER_ERROR", > e); > res.setStatus(HttpServletResponse.SC_INTERNAL_SERVER_ERROR); > } else { > log.error("processAxisFault() found an HTTP status from the > MessageContext instance, setting HttpServletResponse status to: " + status); > res.setStatus(Integer.parseInt(status)); > return; > } {code} > --- > Also these logs with level "error" are spammy - maybe consider a warning > since they are handled - one of our customers complained about thousands of > lines off errors with stacktraces for this recurring conditiion - our custom > fork has these set to warn. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org