Fixes are available
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
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
Document Information
Modified date:
25 October 2021