PM10081: A NullPointerException error may occur while running a JAX-WS application.

Fixes are available

APAR status

Closed as program error.

Error description

A NullPointerException error may occur while running a JAX-WS
application.   This error is likely to occur if the wsdl
operation has a part that is mapped to a header element.

Here is an example error:

ExceptionFact 1 org.apache.axis2.jaxws.ExceptionFactory
logRootCause stack:java.lang.NullPointerException
at
org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils
.getPDElements(MethodMarshallerUtils.java:335)
at
org.apache.axis2.jaxws.marshaller.impl.alt.DocLitBareMethodMarsh
aller.demarshalResponse(DocLitBareMethodMarshaller.java:133)
at
org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.createResp
onse(JAXWSProxyHandler.java:440)
at
org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invokeSEIM
ethod(JAXWSProxyHandler.java:351)
at
org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invoke(JAX
WSProxyHandler.java:159)

Local fix

```
n/a
```

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server V7.0 users *
*                  of JAX-WS                                   *
****************************************************************
* PROBLEM DESCRIPTION: A NullPointerException may occur        *
*                      while running a JAX-WS application      *
*                      that uses header parameters.            *
****************************************************************
* RECOMMENDATION:  Install a fixpack containing this APAR      *
****************************************************************
A NullPointerException error may occur while running a JAX-WS
application.   This error is likely to occur if the wsdl
operation has a part that is mapped to a header element.

Here is an example error:

ExceptionFact 1 org.apache.axis2.jaxws.ExceptionFactory
logRootCause stack:java.lang.NullPointerException
at
org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils
.getPDElements(MethodMarshallerUtils.java:335)
at
org.apache.axis2.jaxws.marshaller.impl.alt.DocLitBareMethodMarsh
aller.demarshalResponse(DocLitBareMethodMarshaller.java:133)
at
org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.createResp
onse(JAXWSProxyHandler.java:440)
at
org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invokeSEIM
ethod(JAXWSProxyHandler.java:351)
at
org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invoke(JAX
WSProxyHandler.java:159)

Most wsdl operations do not have message parts that are
mapped to header elements.

Here is an example of a JAX-WS web method that has @WebParam
mapped to a header.

@WebMethod
@WebResult(name = "String",
           targetNamespace = "http://sample",
           partName = "result")
public String myOperation(
        @WebParam(name = "BodyInteger",
                  targetNamespace = "http://sample",
                  partName = "bodyParam")
        int bodyParam,
        @WebParam(name = "HeaderString",
                  targetNamespace = "http://sample",
                  partName = "headerParam",
                 header=true)
        String headerParam)
    ;



The error will only occur if the header parameter is missing
in the incoming message.

Problem conclusion

The JAX-WS runtime is responsible for marshaling and
unmarshaling the parameters of the web service.  Due to a
missing condition in the runtime, the unmarshaling fails with
a NullPointerExeption if the expected header parameter is
missing.  This condition is corrected, and the JAX-WS runtime
successfully unmarshals the incoming message.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.11.  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
PM10081
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-03-16
Closed date
2010-03-25
Last modified date
2010-03-25

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

PM10081: A NullPointerException error may occur while running a JAX-WS application.

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?