axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Lipp (JIRA)" <j...@apache.org>
Subject [jira] Created: (AXIS2-4364) Error logging is excessive
Date Wed, 03 Jun 2009 08:22:07 GMT
Error logging is excessive
--------------------------

                 Key: AXIS2-4364
                 URL: https://issues.apache.org/jira/browse/AXIS2-4364
             Project: Axis 2.0 (Axis2)
          Issue Type: Bug
          Components: kernel
    Affects Versions: 1.4, 1.4.1
            Reporter: Michael Lipp


If the invocation of the business logic throws an exception that is mapped to a fault response,
the exception is logged as error (AxisEngine.receive(MessageContext msgContext), see end of
the method).

Logging an error usually indicates that something went wrong. From the perspective of the
Axis2 framework, however, everything is perfectly OK. The business logic has thrown an exception,
it is returned to the invoker as a fault, so where's the error? (Compare in contrast the better
handling in AbstractMessageReceiver.receive(final MessageContext messageCtx). Here the exception
is only logged as error if it happens to be an "in only" message exchange, i.e. when the client
cannot be notified about the exception.)

We have a system where exceptions are thrown by the business logic quite frequently (it's
a "customer not registered for this service" situation). While you could argue that we had
better defined a WSDL in which this situation is mapped to some "normal" result instead of
a fault, our definition is perfectly within the SOAP specs. The excessive error messages in
the log, however, result in unnecessary alerts in monitoring. We'll probably have to set the
log level for AxisKernel to FATAL, although we do not like to do this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message