IT42425: MQ Telemetry fails to start and reports an AMQXR0008E containing reason code 2059 (MQRC_Q_MGR_NOT_AVAILABLE)

APAR status

• Closed as program error.

Error description

• An IBM MQ queue manager has been configured to use the
  AutoConfig functionality, and runs an MQSC script containing the
  following commands when it starts up:
  
  DEF SERVICE(SYSTEM.MQXR.SERVICE) +
          CONTROL(QMGR) +
          DESCR('Manages clients using MQXR protocols such as
  MQTT') +
          SERVTYPE(SERVER) +
          STARTCMD('+MQ_INSTALL_PATH+/mqxr/bin/runMQXRService.sh')
  +
          STARTARG('-m +QMNAME+ -d "+MQ_Q_MGR_DATA_PATH+" -g
  "+MQ_DATA_PATH+"') +
          STOPCMD('+MQ_INSTALL_PATH+/mqxr/bin/endMQXRService.sh')
  +
          STOPARG('-m +QMNAME+') +
          STDOUT('+MQ_Q_MGR_DATA_PATH+/mqxr.stdout') +
          STDERR('+MQ_Q_MGR_DATA_PATH+/mqxr.stderr') REPLACE
  
  START SERVICE(SYSTEM.MQXR.SERVICE) IGNSTATE(YES)
  
  to launch the MQ Telemetry service
  
  However, when the queue manager starts up, the MQ Telemetry
  service fails to initialize and reports the error:
  
  AMQXR0008E: Exception during start up of MQTT service:
    com.ibm.mq.communications.UnexpectedExceptionException:
  AMQCO1001E: service unexpectedly caught communications
  exception=com.ibm.mq.MQException: MQJE001: Completion Code '2',
  Reason '2059'.(Exception).
    Caused by: com.ibm.mq.MQException: MQJE001: Completion Code
  '2', Reason '2059'.
  
  in its log file (mqxr_<number>.log).
  

Local fix

• Connecting to MQ server and manually starting the service
  running this command : echo "START
  SERVICE(SYSTEM.MQXR.SERVICE)" | runmqsc QM1 starts correctly.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects users of the IBM MQ Telemetry server.
  
  
  Platforms affected:
  AIX, Windows, Linux on x86-64, Linux on Power, Linux on zSeries
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  If the MQ Telemetry server was started before the queue manager
  had fully completed its initialization and was ready to accept
  connections, then it would write the following error to its log
  file (mqxr_<number>.log) before shutting down:
  
  AMQXR0008E: Exception during start up of MQTT service:
    com.ibm.mq.communications.UnexpectedExceptionException:
  AMQCO1001E: service unexpectedly caught communications
  exception=com.ibm.mq.MQException: MQJE001: Completion Code '2',
  Reason '2059'.(Exception).
    Caused by: com.ibm.mq.MQException: MQJE001: Completion Code
  '2', Reason '2059'.
  

Problem conclusion

• To resolve this issue, some retry logic has been added to the MQ
  Telemetry server so that if it encounters an exception
  containing reason code 2059 (MQRC_Q_MGR_NOT_AVAILABLE) while
  starting up, it will pause for half a second before trying
  again. If the queue manager is still unavailable after 60 retry
  attempts (ie. the server has failed to connect to the queue
  manager after 30 seconds), then it will report the error:
  
  AMQXR0008E: Exception during start up of MQTT service:
    com.ibm.mq.communications.UnexpectedExceptionException:
  AMQCO1001E: service unexpectedly caught communications
  exception=com.ibm.mq.MQException: MQJE001: Completion Code '2',
  Reason '2059'.(Exception).
    Caused by: com.ibm.mq.MQException: MQJE001: Completion Code
  '2', Reason '2059'.
  
  to its log file (mqxr_<number>.log> and shut down.
  
  To disable the retry logic, add the entry:
  
  com.ibm.mq.MQXR.PCFAgentMaxRetryCount=0
  
  to the MQ Telemetry configuration file. The name and location of
  this file is shown below:
  
  AIX or Linux platforms:
  /var/mqm/qmgrs/<queue manager>/mqxr/mqxr_unix.properties
  
  Windows:
  <MQ data directory>\qmgrs\<queue
  manager>\mqxr\mqxr_win.properties
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.3 LTS   9.3.0.5
  v9.x CD    9.3.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

  MQ BASE V9.3

• Fixed component ID

  5724H7291

Applicable component levels