APAR status
Closed as program error.
Error description
After upgrading from IBM MQ V9.0.0.3 to V9.0.0.6, the IBM MQ Telemetry service fails to start and generates an FDC containing the following information: ---------------------------------------------------------------- Source Class :- com.ibm.mq.MQXRService.MQXRService Source Method :- start Probe Id :- XR063035 ... Exception cause: com.ibm.mq.MQXRService.MQException: AMQXR0004E: MQSeriesverb=MQOPEN(String) returned cc=2(int) MQCC_FAILED c=2035(int)MQRC_NOT_AUTHORIZED. at com.ibm.mq.MQXRService.MQConnection.getMQException(MQConnection. java:1252) at com.ibm.mq.MQXRService.MQConnection.open(MQConnection.java:242) at com.ibm.mq.MQXRService.LifecycleMessage.sendMessage(LifecycleMes sage.java:252) at com.ibm.mq.MQXRService.MQXRService.loadPersistentState(MQXRServi ce.java:1238) at com.ibm.mq.MQXRService.MQXRService.start(MQXRService.java:629) at com.ibm.mq.MQXRService.MQXRService.run(MQXRService.java:388) at com.ibm.mq.MQXRService.RunMQXRService.runMQXRService(RunMQXRServ ice.java :195) at com.ibm.mq.MQXRService.RunMQXRService.main(RunMQXRService.java:6 6) ... ----------------------------------------------------------------
Local fix
To workaround the issue, delete the messages from the "SYSTEM.MQTT.PERSISTENT.STATE" queue and then restart the IBM MQ Telemetry service.
Problem summary
**************************************************************** USERS AFFECTED: This issue affects users of the IBM MQ Telemetry service who have MQTT client applications that connect to it, specifying a Last Will and Testament (LWT) message. Platforms affected: Windows, Linux on x86-64, Linux on Power, Linux on S390 **************************************************************** PROBLEM DESCRIPTION: APAR IT23213: https://www.ibm.com/support/docview.wss?uid=swg1IT23213 was included in the MQ 9.0.0.4 fix pack, and MQ 9.1.0.0. It added added logic to the IBM MQ Telemetry service so that: - If an MQTT client application connected to the IBM MQ Telemetry service, and specified a Last Will and Testament (LWT) message. - And the user running that MQTT client application did not have sufficient authority to publish the LWT message to the LWT topic then when the LWT message was processed, it would be removed from the queue: SYSTEM.MQTT.PERSISTENT.STATE and the following message would be written to the IBM MQ Telemetry service log (mqxr.log): AMQXR2067E: An attempt to publish a last will and testament message from Client Identifier '<client id>' on channel '<channel name>' failed as the user identifier '<user id>' performing the operation was not authorized to access the topic '<topic name>'. As a result of these changes, if the IBM MQ Telemetry service was shutdown with last will and testament messages on the queue, and subsequently: - Detected an LWT message on the SYSTEM.MQTT.PERSISTENT.STATE queue when it started up. - And was unable to publish the LWT message to the LWT topic due to an authorization failure. then the IBM MQ Telemetry service would generate an FDC containing the following information: ---------------------------------------------------------------- Source Class :- com.ibm.mq.MQXRService.MQXRService Source Method :- start Probe Id :- XR063035 ... Exception cause: com.ibm.mq.MQXRService.MQException: AMQXR0004E: MQSeriesverb=MQOPEN(String) returned cc=2(int) MQCC_FAILED c=2035(int)MQRC_NOT_AUTHORIZED. ---------------------------------------------------------------- and shut itself down.
Problem conclusion
To resolve this issue, the IBM MQ Telemetry service has been updated so that if it: - Detects a Last Will and Testament (LWT) message on the SYSTEM.MQTT.PERSISTENT.STATE queue while starting up. - And is unable to publish that LWT message to the LWT topic due to an authorization failure. then it will write the message: AMQXR2088E: During startup, an attempt to publish a last will and testament message from Client Identifier ''{0}'' failed as the user identifier ''{1}'' performing the operation was not authorized to access the topic ''{2}''. The message has been deleted. to the IBM MQ Telemetry service log file (mqxr.log) and remove the LWT message from the SYSTEM.MQTT.PERSISTENT.STATE queue. This allows the IBM MQ Telemetry service to start as expected. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v9.0 LTS 9.0.0.8 v9.1 CD 9.1.3 v9.1 LTS 9.1.0.4 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
IT29386
Reported component name
IBM MQ BASE M/P
Reported component ID
5724H7261
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-06-14
Closed date
2019-07-22
Last modified date
2019-07-22
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 M/P
Fixed component ID
5724H7261
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":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
22 July 2019