Direct links to fixes
APAR status
Closed as program error.
Error description
The boundary element in a multi-part HTTP response is invalid. RFC 2046 defines the boundary string to be a maximum of 70 characters. The boundary string generated is 83 characters (for example: boundary=ewdcl-jbgw01.bms.samples.govt.us-2cdde3ca1598aedb8b1-44 03-multipart-boundary-string).
Local fix
STRRTC - 526757 DW / DW Circumvention: None
Problem summary
USERS AFFECTED: ALL PROBLEM DESCRIPTION: MIME Service generates multi-part messages with invalid boundary element (exceeded max 70 char based on RFC 2046). PLATFORMS AFFECTED: ALL
Problem conclusion
RESOLUTION SUMMARY: When the computed boundary is less than 70 chars in length, then the boundary shall still contain the fully qualified hostname in it. In case it exceeds 70 chars, then the boundary will have the short hostname in it. Also as part of fixing this issue we have introduced a new property called fullyQualifiedHostNameInBoundary in adapterSrv.properties file. ## PROPERTY_START ## PROPERTY_NAME: fullyQualifiedHostNameInBoundary ## PROPERTY_TYPE: Boolean ## PROPERTY_DESCRIPTION ## Specifies if the boundary in the mime message should contain the fully qualified host name or not. ## Default value is false, which indicates that the boundary shall not contain the fully qualified host name. ## NOTE : Even though this value is false, if the total length of the computed boundary is less than or equal to 70 chars, then the computed boundary shall still contain the fully qualified hostname. fullyQualifiedHostNameInBoundary=false By default this value is set to false so that the computed boundary does not make use of fully qualified hostname. A sample boundary looks like below when this property is set to false:- example-3351a6f115a441105f6-7b97-boundary When this property is set to true, the older behavior is retained and a sample boundary looks like below :- example.hostname.com-3351a6f115a441105f6-7b97-multipart-boundary -string DELIVERED IN: 5020601_7 5020602_4 5020603_2
Temporary fix
Comments
Published On: 30-Mar-2017
APAR Information
APAR number
IT19188
Reported component name
STR B2B INTEGRA
Reported component ID
5725D0600
Reported release
526
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-02-08
Closed date
2017-03-14
Last modified date
2017-06-19
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
STR B2B INTEGRA
Fixed component ID
5725D0600
Applicable component levels
R526 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2.6","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
19 June 2017