APAR status
Closed as program error.
Error description
When invoking a webservice on Websphere Application Server 6.1 with WebServices Feature Pack using MTOM, the size of files that are sent out have different sizes than those coming back. Upon first inspection, it appears that there is an illegal charset parameter in the message header. This is incorrect, as the overall message for a multipart-related type should not have a charset parameter: Here is the message (with newlines added for readability): Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_264251D281B44957C41181745303768; type="application/xop+xml"; start="<0.urn:uuid:264251D281B44957C41181745303769@apache.org>"; start-info="text/xml"; charset=UTF-8 --------------------------------------------------------- On a content-type header, the charset parameter identifies the character encoding of the body of the corresponding message. At this level, the message has a multipart body. The charset parameter isn't valid in the headers of ANY multipart type. Neither the multipart/related specification nor any example in any specification suggests that it should be allowed. It only applies to text and to text-related formats such as application/xml. The body of a multipart/related document is not text so it cannot have a charset. It is a collection of parts which are required to consist of valid 7-bit ASCII headers combined with data in whatever encoding is specified in the content-type and content-encoding headers for the relevant part.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server users of * * Web Services Feature Pack * **************************************************************** * PROBLEM DESCRIPTION: Invalid parameter in content-Type with * * multipart/related value * **************************************************************** * RECOMMENDATION: * **************************************************************** We can successfully invoke a webservice using MTOM, however when checking the size of the data sent to the data coming back, it is different. The problem is that a content-Type header field with a "multipart/related" value must not include any encoding as a parameter. In the case of the one shown, the charset parameter inclusion is not valid.
Problem conclusion
This fix is targeted for fixpack 6.1.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
PK48897
Reported component name
WEBSERVIC FEATU
Reported component ID
5724J0850
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-07-12
Closed date
2007-08-22
Last modified date
2007-08-22
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
WEBSRVC
Fix information
Fixed component name
WEBSERVIC FEATU
Fixed component ID
5724J0850
Applicable component levels
R610 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
10 February 2022