APAR status
Closed as program error.
Error description
For strings over the length of 2048 characters, the webservices
implementation in IBM WebSphere Application Server wrappers the
string in a CDATA. This leads to problems for certain
WebServices implementations, one being MicroSoft's .NET.
org.xml.sax.SAXParseException: The element type "message" must
be
terminated by the matching end-tag "</message>".; nested
exception is:
parsing error: org.xml.sax.SAXParseException: The
element type
"message" must be terminated by the matching end-tag
"</message>".:
The systemout.log shows the following error:
TRAS0014I: The following exception was logged WebServicesFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client
faultString: parsing error: org.xml.sax.SAXParseException: The
element
type "message" must be terminated by the matching end-tag
"</message>".
faultActor: /PBYShopXTLogBpelWeb/servlet/rpcrouter
faultDetail:
parsing error: org.xml.sax.SAXParseException: The element type
"message"
must be terminated by the matching end-tag "</message>". at
com.ibm.ws.webservices.engine.xmlsoap.builders.SOAPFaultBuilder.
createFault
Local fix Problem summary
****************************************************************
* USERS AFFECTED: Anyone returning long strings in their web *
* services *
****************************************************************
* PROBLEM DESCRIPTION: When a web service returns a string *
* longer than 2048 characters, the *
* string is wrapped in a CDATA field. *
* This causes problems for some customers *
* who may have strange characters in *
* their strings. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
If CDATA is used to wrap the contents of a web services
response, the customer can put invalid characters in there
that would in the end, cause problems during deserialization.
For example, if the customer was returning XML as a the
string contents of the CDATA field, and the string had a
CDATA inside of it, then the parser would not be able to
process the whole message because CDATA sections cannot be
nested.
Problem conclusion
We've removed the CDATA wrapper from all return strings.
Temporary fix Comments
APAR information |
APAR number |
PQ91122 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
10W |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-07-08 |
Closed date |
2004-07-14 |
Last modified date |
2006-07-04 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PK01331
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|