IT17927: IMS CALLOUT HANDLER MIGHT DELAY SENDING RESPONSE BACK TO IMS CONNECT SERVER.
Fixes are available
Closed as program error.
While processing IMS Callout transactions, DataPower might delay (up to 5 seconds) sending back a response message to the IMS Connect server even though the DataPower system and latency logs show the transaction has completed in time. The delay is in getting a new response connection created when the connection pool is empty. This behavior can lead to late delivery of response messages triggering a DataPower error message similar to the following: [0x8c800015][ims][error] source-ims-callout(IMS_Callout_FSH): Fail to deliver response (length: 1748, correlation token 0x0028XXXXXXXXXXXXXXXXXXXXXXXXXX). Error: imsConnectReturnCode =  imsConnectReasonCode =  otmaSenseCode = otmaReasonCode = . If the IMS Callout Handler is configured with a response concurrency of 1 and this issue occurs, response messages might get queued up and delivered by the IMS Callout Handler one at a time with 5 seconds in between each delivery. This behavior might be triggered upon first late delivery of a response message by the IMS Callout Handler due to increased latency on DataPower while processing the transaction.
DataPower user who uses IMS Callout Front Side Handler may take more time to respond the message, if it fails to deliver the response.
Fix is available in 188.8.131.52, 184.108.40.206, 220.127.116.11 and 18.104.22.168 For a list of the latest fix packs available, please see: http://www-01.ibm.com/support/docview.wss?uid=swg21237631
Reported component name
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels