PM20820: An exception thrown within a JAX-WS handler during inbound message processing does not have its root cause in the FFDC

Fixes are available

APAR status

Closed as program error.

Error description

If an exception is thrown during a JAX-WS handler's outbound
message processing, the root cause of the exception will
appear in the FFDC (First Failure Data Capture) log.

However if an exception is thrown during a JAX-WS handler's
inbound message processing, the root cause of the exception
may not appear in the FFDC log.

The missing FFDC information makes it difficult to properly
service the Web service.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server V7.0 users *
*                  of JAX-WS handlers                          *
****************************************************************
* PROBLEM DESCRIPTION: An exception thrown within a JAX-WS     *
*                      handler during inbound message          *
*                      processing does not have its root       *
*                      cause in the FFDC log.                  *
****************************************************************
* RECOMMENDATION:  Install a fix pack containing this APAR     *
****************************************************************
If an exception is thrown during a JAX-WS handler's outbound
message processing, the root cause of the exception will
appear in the FFDC (First Failure Data Capture) log.

However if an exception is thrown during a JAX-WS handler's
inbound message processing, the root cause of the exception
may not appear in the FFDC log.

The missing FFDC information makes it difficult to properly
service the Web service.

Problem conclusion

If a JAX-WS exception is caught during a handler's outbound
message processing, the JAX-WS runtime stores the exception so
that it can be logged correctly.

The JAX-WS runtime is changed to also store the caught
exception if the exception occurs during inbound message
processing.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.15.  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
PM20820
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-08-18
Closed date
2010-10-22
Last modified date
2010-10-22

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

Tips

PM20820: An exception thrown within a JAX-WS handler during inbound message processing does not have its root cause in the FFDC

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?