PM16071: A NullPointerException error may occur when calling an asynchronous JAX-WS Web service.

Fixes are available

APAR status

Closed as program error.

Error description

When making an Asynchronous request to a Web service provider,
the response may return with a SOAPFault, and the client-side
trace may show the following NullPointerException as a result:

java.util.concurrent.ExecutionException:
java.lang.NullPointerException
 at org.apache.axis2.jaxws.client.async.AsyncResponse.onError
(AsyncResponse.java:141)
 at org.apache.axis2.jaxws.client.async.PollingFuture.onError
(PollingFuture.java:95)
 at org.apache.axis2.description.
OutInAxisOperationClient$NonBlockingInvocationWorker.run
(OutInAxisOperation.java:470)
 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask
(ThreadPoolExecutor.java:886)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:736)
Caused by: java.lang.NullPointerException
 at
org.apache.axis2.jaxws.marshaller.factory.MethodMarshallerFactor
y.
getMarshaller(MethodMarshallerFactory.java:106)
 at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.
getFaultResponse(JAXWSProxyHandler.java:473)
 at org.apache.axis2.jaxws.client.proxy.ProxyAsyncListener.
getFaultResponse(ProxyAsyncListener.java:70)
 at org.apache.axis2.jaxws.client.async.AsyncResponse.
processFaultResponse(AsyncResponse.java:431)
 at org.apache.axis2.jaxws.client.async.AsyncResponse.onError
(AsyncResponse.java:129)
 ... 5 more

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server            *
*                  users and administrators of                 *
*                  asynchronous JAX-WS Web services            *
****************************************************************
* PROBLEM DESCRIPTION: A JAX-WS client making an               *
*                      asynchronous call may result in a       *
*                      NullPointerException error.             *
****************************************************************
* RECOMMENDATION:  Install a fix pack that includes this APAR. *
****************************************************************
When making an asynchronous request to a JAX-WS Web service
provider, a NullPointerException error may occur:

Here is a portion of the error:
org.apache.axis2.jaxws.marshaller.factory.MethodMarshallerFactor
y.
getMarshaller(MethodMarshallerFactory.java:106)
at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.
getFaultResponse(JAXWSProxyHandler.java:473)
at org.apache.axis2.jaxws.client.proxy.ProxyAsyncListener.
getFaultResponse(ProxyAsyncListener.java:70)
at org.apache.axis2.jaxws.client.async.AsyncResponse.
processFaultResponse(AsyncResponse.java:431)
at org.apache.axis2.jaxws.client.async.AsyncResponse.onError
(AsyncResponse.java:129)
... 5 more


The error is more likely to occur if the remote Web service
returns a SOAP Fault.

The error will only occur if the wsdl operation name
specified on the @WebMethod of the synchronous method is
different than the method name.  For example:

interface SampleWebService {
    // synchronous method name...note the difference in case
    @WebMethod(operationName = "Echo") throws MyException
    public String echo(String toEcho);

    // matching asynchronous methods
    @WebMethod(operationName = "Echo")
    public Response<String> echoAsync(String toEcho);

    @WebMethod(operationName = "Echo")
    public Future<?> echoAsync(String toEcho,
       AsyncHandler<String> asyncHandler);

}

Problem conclusion

The checked exceptions of a JAX-WS Web service are only
located on the synchronous Web method.  When a Fault is
received by an asynchronous Web method, the JAX-WS runtime must
locate the synchronous Web method to examine the checked
exceptions.

Due to a flaw in the search algorithm, the synchronous Web
method is not found if its operationName is different than the
method name.   The failed search causes the
NullPointerException error.

The search algorithm is corrected, and this scenario will now
succeed.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.13.  Please refer to the Recommended Updates
page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM16071
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-06-07
Closed date
2010-06-23
Last modified date
2010-06-29

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
25 October 2021

Tips

PM16071: A NullPointerException error may occur when calling an asynchronous JAX-WS Web service.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?