PK85804: A JAX-WS WEB SERVICE MAY FAIL WITH A NULLPOINTEREXCEPTION IF THE JAXB CLASSES ARE NOT IN THE APPLICATION

Fixes are available

APAR status

Closed as program error.

Error description

The following error can occur when a JAX-WS application is not
packaged with JAXB classes.


[22-04-09 23:04:05:078 CDT] 00000027 ExceptionFact 1
org.apache.axis2.jaxws.ExceptionFactory
createWebServiceException Create
Exception:

javax.xml.ws.WebServiceException:
java.lang.NullPointerException
at
org.apache.axis2.jaxws.ExceptionFactory.createWebServiceExceptio
n(ExceptionFactory.java:175)
at
org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(
ExceptionFactory.java:70)
at
org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(
ExceptionFactory.java:128)
at
org.apache.axis2.jaxws.marshaller.impl.alt.DocLitWrappedMinimalM
ethodMarshaller.demarshalRequest(DocLitWrappedMinimalMethodMarsh
aller.java:221)

Local fix

Package the JAXB classes with the application

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server V7.0 users *
*                  of JAX-WS applications                      *
****************************************************************
* PROBLEM DESCRIPTION: A NullPointerException may occur if     *
*                      the JAX-WS application does not         *
*                      include JAXB classes.                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Under normal circumstances, a JAX-WS web service application
uses JAXB classes to represent the method and parameter data
for document/literal operations.  However, very simple web
service applications may not contain JAXB classes.

For example, a JAX-WS document/literal method that only has
Java primitive parameters might be developed without JAXB
classes.

Another example is a benchmark application.  A benchmark
application that is developed by other (non-IBM) vendors and
deployed on the Web Sphere Application Server might not
contain JAXB classes

If JAXB classes are not present, the JAX-WS runtime will
perform correctly in most cases.

When the following conditions are met, the JAX-WS runtime will
fail with a NullPointerException error:
   * The JAX-WS web service has a style/use defined as
document/literal.
   * The JAX-WS web service is defined as or defaults to the
wrapped mapping.
   * The JAX-WS web service does not contain JAXB classes.
   * The JAX-WS web service receives a message that indicates
that one of the parameters to the JAX-WS operation is null or
missing.

The NullPointerException will occur when the JAX-WS runtime
receives the incoming message.  Here is an example error:

javax.xml.ws.WebServiceException:
java.lang.NullPointerException
at
org.apache.axis2.jaxws.ExceptionFactory.createWebServiceExceptio
n(ExceptionFactory.java:175)
at
org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(
ExceptionFactory.java:70)
at
org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(
ExceptionFactory.java:128)
at
org.apache.axis2.jaxws.marshaller.impl.alt.DocLitWrappedMinimalM
ethodMarshaller.demarshalRequest(DocLitWrappedMinimalMethodMarsh
aller.java:221)

Problem conclusion

The JAX-WS runtime has two separate algorithms for operations
defined as document/literal/wrapped.

The "Document Literal Wrapped Minimal" algorithm is used when
the JAXB classes are not present.
The "Document Literal Wrapped" algorithm is used when the JAXB
classes are present.

The "Document Literal Wrapped Minimal" algorithm did not
support incoming messages that contain null or missing
parameters.  The algorithm was improved to add this additional
support, and the NullPointerException will no longer occur.

Note that the "Document Literal Wrapped" algorithm was not
changed.  That algorithm already supports incoming messages
with null or missing parameters.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.7.  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
PK85804
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-05-01
Closed date
2009-06-12
Last modified date
2009-06-12

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
WEBS APP SERV N
Fixed component ID
5724H8800

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:
24 October 2021

Tips

PK85804: A JAX-WS WEB SERVICE MAY FAIL WITH A NULLPOINTEREXCEPTION IF THE JAXB CLASSES ARE NOT IN THE 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?