cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aki Yoshida (JIRA)" <>
Subject [jira] Created: (CXF-3349) NPE may be thrown in WS-RM scenarios at the server side when rebasing the response
Date Fri, 18 Feb 2011 16:53:38 GMT
NPE may be thrown in WS-RM scenarios at the server side when rebasing the response

                 Key: CXF-3349
             Project: CXF
          Issue Type: Bug
          Components: WS-* Components
    Affects Versions: 2.3.2
            Reporter: Aki Yoshida
             Fix For: 2.4, 2.3.3

Some WS-RM scenarios may sometimes result in the following exception at the provider/server
side under the piggyback mode..

java.lang.NullPointerException: null
 at$2.getBackChannel( ~[org.apache.cxf.cxf-bundle-2.3.2.jar:2.3.2]
 at org.apache.cxf.interceptor.OneWayProcessorInterceptor.handleMessage(
 at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(
 at org.apache.cxf.transport.ChainInitiationObserver.onMessage(

The cause of this problem seems to be in the rebaseResponse method of,
where the destination endpoint is determined in the following code:
421                     Destination destination = createDecoupledDestination(
422                         exchange, reference);
423                     exchange.setDestination(destination);

As this reference parameter could become null, it needs a similar handling as in the code
a few lines above:
388                                                             reference == null
389                                                             ? ContextUtils.getNoneEndpointReference()
390                                                             : reference 
Alternatively, the reference variable can be set to ContextUtils.getNoneEndpointReference()
at the beginning of this rebaseResponse method to prevent this problem.

This problem does not occur in 2.2.x because this second use/reference of the referece variable
is only present in 2.3.x.

I believe this change will solve this issue.

Regards, aki

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message