APAR status
Closed as program error.
Error description
When connecting an application to a queue manager running on Windows, the connection fails with MQRC_RESOURCE_PROBLEM if the server is under high load. In this scenario, the error log shows: AMQ9772: MQCTL failed with MQRC=2102. Explanation: The indicated IBM MQ API call failed for the specified reason code. MQ trace of the problem shows xecX_E_RESOURCE_ERROR from call to xcsConnectSimplePipe, with an "all instances busy" message, similar to below: --------------{ xcsConnectSimplePipe ---------------{ xcsGetMemFn component:24 function:466 length:328 options:0 cbmindex:0 *pointer:0000003D3DB3DBB0 ---------------} xcsGetMemFn (rc=OK) Pipe \\.\pipe\mqm.1.qmgrs.<QMNAME>.4.pipe.signalapp all instances busy (231) ---------------{ xcsFreeMemFn component:24 pointer:0000003D3DB3DBB0 cbmindex:0 ---------------} xcsFreeMemFn (rc=OK) --------------}! xcsConnectSimplePipe (rc=xecX_E_RESOURCE_ERROR)
Local fix
Problem summary
**************************************************************** USERS AFFECTED: Users who are connecting a high volume of applications to a queue manager on Windows. The issue was observed when connecting a large number of server-bound MQ applications, but could in theory affect channel programs if a large volume of channel agents were started concurrently. Platforms affected: Windows **************************************************************** PROBLEM DESCRIPTION: In the event of contention for internal IPC resources, it is expected that these attempts are retried for a period of 30 seconds. A programming error resulting in a timing window whereby the MQ queue manager could fail to retry all requests correctly if contention was detected.
Problem conclusion
MQ now allows the full retry period to expire before timing out the connection with MQRC_RESOURCE_PROBLEM. MQRC_RESOURCE_PROBLEM will continue to be output with additional appropriate information if connections cannot be accepted due to system resource issues. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v9.0 LTS 9.0.0.6 v9.1 CD 9.1.2 v9.1 LTS 9.1.0.2 The latest available maintenance can be obtained from 'WebSphere MQ Recommended Fixes' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 If the maintenance level is not yet available information on its planned availability can be found in 'WebSphere MQ Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT25426
Reported component name
IBM MQ BASE M/P
Reported component ID
5724H7261
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-06-20
Closed date
2019-01-31
Last modified date
2019-01-31
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
IBM MQ BASE M/P
Fixed component ID
5724H7261
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
31 January 2019