IT17039: Enabling activity trace causes FDCs to be written and no activity trace messages are sent

APAR status

• Closed as program error.

Error description

• After enabling activity tracing when using WebSphere MQ v7.5
  FDCs are created similar to the snippet below.
  
  No activity trace messages are put to the
  SYSTEM.ADMIN.TRACE.ACTIVITY.QUEUE
  
  FDC snippet:
  
  Probe Id          :- XC130004
  Component         :- xehExceptionHandler
  Program Name      :- amqzlaa0
  Probe Description :- AMQ6109: An internal WebSphere MQ error has
                       occurred.
  Arith1            :- 11 (0xb)
  Comment1          :- SIGSEGV: address not mapped((nil))
  with
  MQM Function Stack
  zlaMainThread
  zlaProcessMessage
  zlaProcessMQIRequest
  zlaMQCB
  zsqMQCB
  kpiMQCB
  kqiRegisterConsumer
  xcsFFST
  

Local fix

• Check the mqat.ini file for syntax errors and correct any that
  are found.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users of MQ activity trace that use a custom mqat.ini file may
  be affected by this problem.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  If an mqat.ini file is used to control IBM MQ activity trace and
  that file contains a syntax error then a SIGSEGV is generated
  due to IBM MQ accessing a bad pointer.  This SIGSEGV occurs
  during the processing of the MQCLOSE activity trace point
  

Problem conclusion

• A syntax error in mqat.ini should cause activity tracing to be
  suppressed and so the code was corrected to avoid calling the
  MQCLOSE activity trace point if tracing is suppressed.  This
  change meant that the bad pointer access could no longer occur.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v7.5       7.5.0.8
  v8.0       8.0.0.6
  v9.0 CD    9.0.1
  v9.0 LTS   9.0.0.1
  
  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

  WMQ BASE MULTIP

• Fixed component ID

  5724H7241

Applicable component levels