PK85110: UNMARSHALL FAILS WITH NULLPOINTEREXCEPTION AFTER 1ST REQUEST RECEIVED FOR ONE OF TWO OPERATIONS DEFINED IN A WSDL

Fixes are available

APAR status

Closed as program error.

Error description

Unmarshall fails with a NullPointerException error on the
second and subsequent requests received for one of two
operations defined in a wsdl. This happens during the
webservices SOAP request processing.


Here is the NullPointerException that is seen in the response
message.

- <soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
- <soapenv:Body>
- <soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring>java.lang.NullPointerException</faultstring>
</soapenv:Fault>
</soapenv:Body>>
</soapenv:Envelope>

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All IBM WebSphere Application Server V7.0   *
*                  users of JAX-WS or JAXB                     *
****************************************************************
* PROBLEM DESCRIPTION: The IBM JAXB runtime may incorrectly    *
*                      unmarshall XML                          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The JAXB runtime reads xml data and creates java beans.  This
process is called unmarshalling. The JAX-WS runtime uses JAXB
unmarshalling for most incoming web service messages.

If the target java beans inherit fields from other java beans,
the IBM JAXB runtime may fail to place values in these fields.

The JAX-WS or JAXB application that interacts with these java
beans may fail in unexpected ways.  The most common error is a
NullPointerException error within the customer's application.

Due to the design of the JAX-WS runtime, the first web service
invocation may pass and subsequent web service invocations may
fail.  This is one of the symptoms of this problem.

Problem conclusion

The IBM JAXBContext object controls the unmarshalling of xml
data.  When the JAXBContext is initialized, it loads
information about all of the target java bean classes.  Due to
errors in the JAXBContext implementation, some of the java
bean base classes were not loaded.  The algorithm is improved
to ensure that these classes are now loaded.

In addition, the computation of the "##default"
namespace for element properties is corrected to
always looks for the namespace in the class and package
where it was declared.  The namespace of properties in the
base class were sometimes being assigned the one from the
derived class, causing some values to be lost because the JAXB
Unmarshaller was expecting the wrong namespace.

The combination of these fixes corrects the problem.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.5.  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
PK85110
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-04-21
Closed date
2009-05-13
Last modified date
2009-05-13

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

PK90751

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

Tips

PK85110: UNMARSHALL FAILS WITH NULLPOINTEREXCEPTION AFTER 1ST REQUEST RECEIVED FOR ONE OF TWO OPERATIONS DEFINED IN A WSDL

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?