JAX-WS: Secondary error occurs while processing AsncResponse
------------------------------------------------------------
Key: AXIS2-4606
URL: https://issues.apache.org/jira/browse/AXIS2-4606
Project: Axis2
Issue Type: Bug
Components: jaxws
Reporter: Rich Scheuerle
Assignee: Rich Scheuerle
While processing a JAX-WS aysnchronous response, a NullPointerException may
occur in the onError method of the jaxws AsyncResponse object.
This is an exception that occurs while processing an exception and leads to
instability in the system.
For example it may lead to a hung system if the caller does not adequately
account for such secondary errors.
protected void onError(Throwable flt, MessageContext faultCtx) {
if (log.isDebugEnabled()) {
log.debug("AsyncResponse received a fault.");
}
fault = flt;
faultMessageContext = faultCtx;
faultMessageContext.setEndpointDescription(endpointDescription);
<--------------------NPE occurs here.
Proposed Solution:
The code will be changed to check for a null faultMessageContext before using
it. A null faultMessageContext is an indication that the onError is processing
a local exception (versus an error from an Endpoint's SOAP Fault).
The onError method will also be hardened to catch other other errors and
respond gracefully. Throwing secondary exceptions from onError leads to system
instability.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
