IT16230: MQ8: AMQP SERVICE ON WINDOWS STOPS WHEN MCA USER ID IS BLANK ANDAMQXR2051E IS ISSUED.

APAR status

• Closed as program error.

Error description

• AMQP service on Windows stops when MCA user id on the channel is
  blank and AMQXR2051E is issued.
  If MCA userid is filled in, all works well.
  
  The following errors can be observed in the error log:
  
  AMQXR0016I: The 'TEST' channel was started
  AMQXR2051E: Login failed for Client Identifier null
              javax.security.auth.login.LoginException: Null
  userName.
  AMQ5029: Service 'SYSTEM.AMQP.SERVICE' terminated. Process ID(
  3048 ).
  
  The following FDC may also be observed:
  
  WebSphere MQ First Failure Symptom Report
  Operating System  :- Windows Server 2012 R2 Server Datacenter
  Edition, Build 9200
  LVLS              :- 8.0.0.4
  Product Long Name :- WebSphere MQ for Windows (x64 platform)
  Probe Id          :- ZX005022
  Component         :- zxcProcessChildren
  UserID            :- MUSR_MQADMIN
  Process Name      :- C:\Program
  Files\IBM\WebSphereMQ\bin64\amqzxma0.exe
  Major Errorcode   :- lrcW_S_FAST_PATH_APP_DEAD
  Minor Errorcode   :- OK
  Probe Type        :- MSGAMQ7159
  Probe Description :- AMQ7159: A FASTPATH ??application
  terminated unexpectedly.
  
  MQM Function Stack
  amqzxma0
  zxcExecutionController
  zxcProcessChildren
  xcsFFST
  
  Data: 0x00000508
  -} xcsCheckProcess rc=xecP_E_INVALID_PID
  -{ xcsBuildDumpPtr
  --{ xcsGetMemFn
  --} xcsGetMemFn rc=OK
  -} xcsBuildDumpPtr rc=OK
  -{ xcsBuildDumpPtr
  -} xcsBuildDumpPtr rc=OK
  -{ xlsRequestMutex
  -} xlsRequestMutex rc=OK
  -{ xcsGetMemFn
  -} xcsGetMemFn rc=OK
  -{ xcsBuildDumpPtr
  -} xcsBuildDumpPtr rc=OK
  -{ xcsBuildDumpPtr
  -} xcsBuildDumpPtr rc=OK
  -{ xcsFFST
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users using the AMQP listener to handle MQTT connections
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The AMQP listener did not correctly handle the case where an
  MQTT channel was in use, and made an illegal memory access.
  

Problem conclusion

• The AMQP listener has been corrected to avoid making an illegal
  memory access when handling MQTT channels.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v8.0       8.0.0.5
  
  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

  5724H7251

Applicable component levels

• R800 PSY

     UP