PM05435: JAX-WS ASYNCHRONOUS CLIENT CALL MAY HANG AND ISSUE A NULLPOINTEREXCEPTION WHEN RECEIVING AN INVALID SOAP RESPONSE

Fixes are available

APAR status

Closed as program error.

Error description

A customer is testing the exception handling of the WebSphere
Application Server's JAX-WS runtime.

One of the customer's test web services intentionally returns
an ill-formed SOAP message.  The customer's JAX-WS asynchronous
client application does not complete.  The client application
appears to be in a hung state.

In addition, the following error might be observed:
java.lang.NullPointerException at
org.apache.axis2.jaxws.client.async.AsyncResponse.onError(AsyncR
esponse.java:106) at
org.apache.axis2.jaxws.client.async.PollingFuture.onError(Pollin
gFuture.java:97)
...

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server V7.0 users *
*                  of asynchronous JAX-WS applications         *
****************************************************************
* PROBLEM DESCRIPTION: A NullPointerException error and a      *
*                      hang state may occur when an            *
*                      asynchronous JAX-WS client processes    *
*                      an invalid XML response.                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When a JAX-WS application receives an invalid response, the
JAX-WS runtime should throw an appropriate specification
defined exception.

In this particular scenario, an ill-formed response is received
by a JAX-WS asynchronous client.  During the processing of the
exception, a secondary error(NullPointerException) occurs:

java.lang.NullPointerException at
org.apache.axis2.jaxws.client.async.AsyncResponse.onError(AsyncR
esponse.java:106) at
org.apache.axis2.jaxws.client.async.PollingFuture.onError(Pollin
gFuture.java:97)
...

This secondary exception is not handled properly, which may
result in a hung application.

Problem conclusion

The JAX-WS runtime contains code to build and throw an
exception when an error occurs.  During this processing, a
secondary error (NullPointerException) occurs in the onError
method.

The NullPointerException error in the onError method is due to
an invalid conditional test.  The condition is corrected.  In
addition, the onError method is hardened to gracefully
tolerate other unanticipated secondary exceptions.  These
changes allow onError to complete successfully, which
eliminates the hung application problem.


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
PM05435
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-01-18
Closed date
2010-02-10
Last modified date
2010-02-10

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

PM05435: JAX-WS ASYNCHRONOUS CLIENT CALL MAY HANG AND ISSUE A NULLPOINTEREXCEPTION WHEN RECEIVING AN INVALID SOAP RESPONSE

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?