This build actually failed because of a mismatch between the Axis2 and
Axiom versions. Interestingly, the only trace of the error in the logs
is this:
9 [main] DEBUG org.apache.synapse.transport.nhttp.Axis2HttpRequest -
Remote server aborted request being sent, and responded
The exception handling is done by the following piece of code in
Axis2HttpRequest:
Integer errorCode = msgContext == null ? null :
(Integer) msgContext.getProperty(NhttpConstants.ERROR_CODE);
if (errorCode == null || errorCode == NhttpConstants.SEND_ABORT) {
if (log.isDebugEnabled()) {
log.debug("Remote server aborted request being sent, and responded");
}
} else {
if (e instanceof AxisFault) {
throw (AxisFault) e;
} else {
handleException("Error streaming message context", e);
}
}
Since the exception occurs in Axis2 (SOAPMessageFormatter) which
doesn't know anything about the NHTTP transport, errorCode is
obviously null in this case. I would expect this kind of exception to
be rethrown instead of just causing a debug log. What is the rationale
for the errorCode == null condition in the if statement?
Andreas
On Sun, Nov 14, 2010 at 12:58, Apache Hudson Server
<[email protected]> wrote:
> See
> <https://hudson.apache.org/hudson/job/Synapse%20-%20Trunk/org.apache.synapse$synapse-nhttp-transport/2901/>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
