PK67941: A JAX-RPC WEB SERVICE IS INCORRECTLY SERIALIZING THE NULL CHARACTER IN A SOAP MESSAGE.

Fixes are available

APAR status

Closed as program error.

Error description

Lightweight Directory Access Protocol (LDAP) server returns
"&#0;", a reference to a null in the SOAP fault string, which
is invalid in XML.
Error seen at client:
javax.xml.soap.SOAPException: org.xml.sax.SAXParseException.

The problem was observed in WebSphere Application Server
v6.0.2.x

In addition the problem is also seen for NON LDAP users as well
where the SOAP message recieved has the incorrect &#0; character
causing WebSphere to throw the exception:

Exception Stack:
----------------------------------------------------------------
org.xml.sax.SAXParseException: Character reference "&#0" is an
invalid XML character.
 at
com.ibm.ws.webservices.engine.WebServicesFault.makeFault(WebServ
icesFault.java:282)
 at
com.ibm.xml.soapsec.proxy.FaultProxy.makeFault(FaultProxy.java:8
4)
 at
com.ibm.xml.soapsec.proxy.ProxyBase.throwException(ProxyBase.jav
a:62)
 at
com.ibm.xml.soapsec.proxy.WASMessageProxyImpl.getDocument(WASMes
sageProxyImpl.java:92)
 at
com.ibm.xml.soapsec.SoapSecuritySender.invoke(SoapSecuritySender
.java:252)
 at
com.ibm.ws.webservices.wssecurity.handler.WSSoapSecuritySenderBa
se.invoke(WSSoapSecuritySenderBase.java:253)
----------------------------------------------------------------

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  All WebSphere Application Server users of   *
*                  JAX-RPC web services                        *
****************************************************************
* PROBLEM DESCRIPTION: The JAX-RPC runtime is incorrectly      *
*                      serializing a null character in a       *
*                      SOAP message.                           *
****************************************************************
* RECOMMENDATION:  Install a fix pack containing this APAR.    *
****************************************************************
If JAX-RPC Web service returns String data that contains a
null character, the null character is automatically serialized
as "&#0;".   This is not a valid xml character, the client
receiving the message will fail.  Normally the client will
fail with a SAXParseException.

Note that there is no legal mapping for a null character to xml.

Problem conclusion

A new JVM custom property has been created to handle this
scenario:

com.ibm.ws.webservices.serializerNullHandling

This JVM custom property can be set to one of two values:
USE_NULL_STRING or IGNORE_NULL.

If set to USE_NULL_STRING, the Web Services code will replace
the null character in the SOAP message with a "{null}" string.

If set to IGNORE_NULL, the Web Services code will simply
ignore the null character in the SOAP message.

The fix for this APAR is currently targeted for inclusion in
fixpacks 6.0.2.33 and 6.1.0.21.  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
PK67941
Reported component name
WEBSPH APP SERV
Reported component ID
5724J0800
Reported release
60A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-06-20
Closed date
2008-09-04
Last modified date
2010-09-16

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
WEBSPH APP SERV
Fixed component ID
5724J0800

Applicable component levels

R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z 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":"6.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 December 2021

Tips

PK67941: A JAX-RPC WEB SERVICE IS INCORRECTLY SERIALIZING THE NULL CHARACTER IN A 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

R60A PSY

R60H PSY

R60I PSY

R60P PSY

R60S PSY

R60W PSY

R60Z PSY

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

Document Information

Share your feedback

Need support?