IT24186: The MQ V8 Command Server process fails with an access violation when attempting to inquire on channel status

APAR status

• Closed as program error.

Error description

• The MQ V8 Command Server process fails with an Access Violation
  (segmentation fault).
  
  The header of the resulting FDC looks like the following:
  
  +---------------------------------------------------------------
  
  | WebSphere MQ First Failure Symptom Report
  | =========================================
  ...
  | Probe Id          :- XC130031
  | Application Name  :- MQM
  | Component         :- xehExceptionHandler
  | SCCS Info         :-
    F:\build\slot1\p800_P\src\lib\cs\pc\winnt\amqxerrn.c,
  | Line Number       :- 767
  | Build Date        :- Jun 29 2017
  | Build Level       :- LAIT23576-198506
  | Build Type        :- IKAP - (Production)
  | UserID            :- MUSR_MQADMIN
  | Process Name      :- D:\mydir\IBM_MQ\IBM\WebSphere MQ
                         \bin64\amqpcsea.exe
  | Arguments         :- TEST
  | Addressing mode   :- 64-bit
  | Process           :- 00016100
  | Thread            :- 00000001    CommandServer
  | Session           :- 00000000
  | QueueManager      :- TEST
  | UserApp           :- FALSE
  | ConnId(1) IPCC    :- 42
  | Last HQC          :- 1.6.6-119872
  | Last HSHMEMB      :- 1.0.0-1839168
  | Last ObjectName   :-
  | Major Errorcode   :- xecF_E_UNEXPECTED_SYSTEM_RC
  | Minor Errorcode   :- OK
  | Probe Type        :- MSGAMQ6119
  | Probe Severity    :- 2
  | Probe Description :- AMQ6109: An internal WebSphere MQ error
                         has occurred.
  
  | FDCSequenceNumber :- 0
  | Comment1          :- Access Violation at address
                         0000000000000000
                         when reading
  +-----------------------------------------------------------
  ---> Stack dump for the faulting thread (0x13B0) <---
  
  
  
  An Unhandled Exception detected in process 16100, on thread
  0x13B0.
  Type: EXCEPTION_ACCESS_VIOLATION (C0000005).
  Address: 0033:00007FFA04AC4940.
  The thread could not read from memory address
  0x0000000000000000.
  MQM Function Stack
  pcmMain
  pcmCommandServer
  pcmProcessMessage
  pcmProcessChannelCommand
  pcmHandleCommand
  pcmInquireChannelStatus
  xcsFFST
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users of the display channel status command may be affected by
  this problem
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The IBM MQ code which is responsible for formatting times was
  passed an invalid value, if a bad channel status record was
  encountered.  This invalid value was incorrectly handled and a
  segmentation violation occurred.
  

Problem conclusion

• The time formatting code has been corrected so it is able to
  cope with an invalid time value, and ignore the invalid record.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v8.0       8.0.0.11
  v9.0 LTS   9.0.0.6
  v9.1 CD    9.1.1
  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 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