APAR status
Closed as program error.
Error description
If an MQ AMS client attempts to reconnect to a queue manager after receiving a connection failure (MQRC_CONNECTION_QUIESCING / MQRC_CONNECTION_BROKEN) then the MQCONNX call can fail with ProbeID XC006001. The FDC footprint will look similar to the following: +--------------------------------------------------------------- --------------+ | | | IBM MQ First Failure Symptom Report | | ========================================= | | | | Date/Time :- Wed April 25 2018 04:36:29 GMT Summer Time | | UTC Time :- 1524627389.931000 | | UTC Time Offset :- 60 (GMT Summer Time) | | Host Name :- XXXXXXXX | | Operating System :- Windows 8.1 Enterprise x64 Edition, Build 9200 | | PIDS :- 5724H7251 | | LVLS :- 9.0.0.3 | | Product Long Name :- IBM MQ for Windows (x64 platform) | | Vendor :- IBM | | O/S Registered :- 1 | | Data Path :- C:\ProgramData\IBM\MQ | | Installation Path :- C:\Program Files (x86)\IBM\Websphere MQ | | Installation Name :- Installation1 (1) | | License Type :- Unknown | | Probe Id :- XC006001 | | Application Name :- MQM | | Component :- xcsFreeMemFn | | SCCS Info :- F:\build\slot1\p900_P\src\lib\cs\amqxspga.c, | | Line Number :- 685 | | Build Date :- Feb 26 2018 | | Build Level :- p900-003-180226 | | Build Type :- IKAP - (Production) | | UserID :- xxxxxxx | | Process Name :- program_name.exe | | Arguments :- | | Addressing mode :- 32-bit | | Process :- 0000nnnn | | Thread :- 0000000n | | Session :- 0000000n | | UserApp :- TRUE | | Last HQC :- 0.0.0-0 | | Last HSHMEMB :- 0.0.0-0 | | Last ObjectName :- | | Major Errorcode :- xecS_I_PRIVATE_MEMORY_ERROR | | Minor Errorcode :- OK | | Probe Type :- MSGAMQ6091 | | Probe Severity :- 4 | | Probe Description :- AMQ6091: An internal IBM MQ error has occurred. | | FDCSequenceNumber :- 0 | | Arith1 :- 15074304 e60400 | | Comment1 :- invalid head tag | | | +--------------------------------------------------------------- --------------+ MQM Function Stack MQCONNX MQCONNX trmzstMQCONNX reqDoConnect reqFreeConn smqxDiscAfter smqiDiscAfter zutLookupIterate smqiFreeObjectCallback xcsFreeMemFn xcsFFST Because of the imprecise timing of events following MQRC_CONNECTION_QUIESCING, other potential errors can occur if the client application issues further MQ API calls.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: Users of non-Java applications which make connections to MQ using a server connection channel, and which are performing AMS interception. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: When the connection between a queue manager and an attached MQ AMS client application fails the client receives either MQRC_CONNECTION_FAILED or MQRC_CONNECTION_QUIESCING. Due to a logic omission, if the client attempted further MQ API operations at this point, the AMS resources allocated by earlier API calls were not cleaned up in the correct sequence. This caused errors including the ProbeId XC006001 from xcsFreeMemFn.
Problem conclusion
The MQ AMS client code has been modified to release allocated resources in the correct sequence following connection problems. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v8.0 8.0.0.14 v9.0 CD 9.0.3 v9.0 LTS 9.0.0.8 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
IT25685
Reported component name
IBM MQ BASE MP
Reported component ID
5724H7251
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-07-13
Closed date
2019-09-30
Last modified date
2019-11-27
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 MP
Fixed component ID
5724H7251
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":"8.0.0.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
27 November 2019