PM81412: WEB SERVICE RESPONSE MESSAGE IS MISSING NAMESPACE IN AN ELEMENT

Fixes are available

APAR status

Closed as program error.

Error description

A JAX-WS web service provider running within WebSphere
Application Server may intermittently send SOAP response
messages to the web service client that are missing a namespace
within an element.  For example:

Expected element:
<item xsi:type="ns2:myItem"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

Incorrect element without the namespace:
<item xsi:type="locationReferenceItem"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server using Axis2 as WebServices server    *
****************************************************************
* PROBLEM DESCRIPTION: WebServices axis2 response is missing   *
*                      namespace prefix intermittently at      *
*                      "xsi:type" element                      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Normally at client side we get an axis2 good response like:
<item xsi:type="ns2:locationReferenceItem"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
However, after the server has been recycling for couple of
days, the wrong response may return:
<item xsi:type="locationReferenceItem"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
Payload is not appended with the namespace prefix. Sometimes,
a ClassCastException may occur as well.
The issue will disappear after the server restarts.

Problem conclusion

In IBM Axis2, there are two methods that will invoke
JAXBContext generation. The first method uses the correct
webs ervice namespace to generate JAXBContext, the other one
does not. JAXBContext is cached by SoftReference, which may be
collected by the JVM if there is not enough system memory.
When the softreference with the JAXBContext is collected by the
jvm, a new JAXBContext needs to be constructed. If the new
JAXBContex is generated in the first method, the issue would
not appear. However, if the new JAXBContex is created in the
second method, the problematic JAXBContext would be created.
During marshalling, the response would lose the namespace
prefix. The second method has been corrected.

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.31, 8.0.0.7 and 8.5.5.1.
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
PM81412
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-01-24
Closed date
2013-04-16
Last modified date
2013-04-23

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
R800 PSY
UP
R850 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
11 January 2022

Tips

PM81412: WEB SERVICE RESPONSE MESSAGE IS MISSING NAMESPACE IN AN ELEMENT

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

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?