Direct link to fix
APAR status
Closed as program error.
Error description
When you call multiple external destinations, for example service1.ibm.com and service2.ibm.com, by using one proxy by SCA HTTP binding, you might notice that some of the requests failed and you received the Error 400 - BadRequest response. You might see the following error message in the log file of the external destinations: Hostname service1.ibm.com provided via SNI and hostname service2.ibm.com provided via HTTP are different
Local fix
n/a
Problem summary
This issue occurs because generating the keys for the connections in the connection pool that is maintained by the SCA HTTP binding was based on the proxy host name only, not including the destination host name. As a result, some connections for destination A in the pool could be re-used for destination B.
Problem conclusion
A fix that can generate the correct key for the connections in the connection pool is available for IBM BPM V8.6.0.0 cumulative fix 2018.03.
Temporary fix
Comments
APAR Information
APAR number
JR62007
Reported component name
BPM
Reported component ID
5737A5700
Reported release
860
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-02-13
Closed date
2020-03-03
Last modified date
2020-03-03
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
BPM
Fixed component ID
5737A5700
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFPJS","label":"IBM Business Process Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.6.0.0","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
14 September 2022