PM09339: THE JAX-WS RUNTIME ISSUES A CONFUSING ERROR WHEN IT RECEIVES AN INVALID SOAP MESSAGE

Fixes are available

APAR status

Closed as program error.

Error description

The IBM WebSphere Application Server JAX-WS runtime received
an invalid SOAP message from a remote node.  The JAX-WS runtime
issued an error message that was confusing.

In the customer's scenario, the incoming SOAP message did not
contain an xml declaration for a prefix (p).  The runtime
responded with the confusing error message:

javax.xml.stream.XMLStreamException: Attribute
name "foo" must be followed by the '=' character.

The runtime should have responded with an error message
similar to:

javax.xml.stream.XMLStreamException: The namespace prefix "p"
was not declared.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server V7.0 users *
*                  of JAX-WS                                   *
****************************************************************
* PROBLEM DESCRIPTION: The JAX-WS runtime issues a confusing   *
*                      message when an invalid SOAP message    *
*                      is received.                            *
****************************************************************
* RECOMMENDATION:  Install a fixpack containing this APAR.     *
****************************************************************
When the IBM WebSphere Application Server JAX-WS runtime
receives an invalid SOAP message from a remote node, the
JAX-WS runtime issues an error message that is confusing.

For example, if the incoming SOAP message does not
contain an xml declaration for a prefix (p).  The runtime
responds with a confusing error message:

javax.xml.stream.XMLStreamException: Attribute
name "foo" must be followed by the '=' character.

The runtime should respond with an error message similar to:

javax.xml.stream.XMLStreamException: The namespace prefix "p"
was not declared.

Note: If the incoming message is invalid for a different
reason, the JAX-WS runtime may respond with an error different
than the one listed above.

Problem conclusion

The JAX-WS runtime uses a StAX parser to receive the incoming
message.  If the StAX parser encounters an error, it will
throw an exception and leaves the StAX parser in an invalid
state.  Subsequent uses of the StAX parser may cause the
parser to throw other (confusing) errors.

The JAX-WS runtime is changed to remember the state of the
StAX parser.  If the parser is in an invalid state, it will
not be used and the prior exception will be re-thrown.  This
fix ensures that the customer will see the original error.

This same problem is fixed in the Feature Pack for Web Services
by APAR PM09337.


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
PM09339
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-08
Closed date
2010-03-22
Last modified date
2010-03-22

APAR is sysrouted FROM one or more of the following:

PM09337
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

PM09339: THE JAX-WS RUNTIME ISSUES A CONFUSING ERROR WHEN IT RECEIVES AN INVALID SOAP MESSAGE

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?