Troubleshooting
Problem
When all of the configured MQ FSH concurrent connections are in use, the next request fails. Why does the MQ FSH immediately reject requests when the concurrent connection count is exceeded?
Symptom
With a simple xslt stylesheet or GatewayScript file, an MQ urlopen does a PUT to the MQ request queue. The MQ FSH of a target DataPower service initiates a GET on the request message from the request queue, but the MQ FSH immediately responds with a SOAP fault.
If the MQ front side handler of the target DataPower service has concurrent connections set to 1, requests alternately succeed and fail. If you increase the concurrent connections value to 5, then 5 requests succeed, and the 6th request fails.
The back-end service does not show the failing request in the probe or in the log. A packet capture between the appliance and the MQ server shows the generic SOAP fault:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Body>
<env:Fault>
<faultcode>env:Client</faultcode>
<faultstring>Internal Error (from client)</faultstring>
</env:Fault>
</env:Body>
</env:Envelope>
[{"Product":{"code":"SS9H2Y","label":"IBM DataPower Gateway"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"--","Platform":[{"code":"PF009","label":"Firmware"}],"Version":"7.2","Edition":"","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
08 June 2021
UID
swg21883941