APAR status
Closed as program error.
Error description
The channel attribute "AMQP keep alive" (AMQPKA) is incorrectly documented as being in seconds - the value is actually in milliseconds. This means that the maximum allowed value of 99999 for this attribute is much smaller than expected, as this is in milliseconds rather than seconds. There are also potentially different intervals for AMQP keep alive frames being sent from the queue manager's AMQP service across the network connection to the client than those expected based on the value of AMQPKA set.
Local fix
NA
Problem summary
**************************************************************** USERS AFFECTED: This issue affects users of the MQ AMQP service, who have set the AMQP channel attribute "AMQP keep alive" (AMQPKA) to a value greater than zero. Platforms affected: AIX, Linux on Power, Linux on x86-64, Linux on zSeries, Solaris x86-64, Solaris SPARC, Windows, HP-UX Itanium **************************************************************** PROBLEM DESCRIPTION: The IBM MQ AMQP channel attribute "AMQP keep alive" (AMQPKA) was defined as being in seconds at V8. The maximum value for the property was 99999 seconds. In IBM MQ V9.0 and V9.1. the "AMQPKA keep alive" value was set in milliseconds. However, the documentation for the attribute in the IBM MQ V9.0.x and V9.1.x sections of IBM Knowledge Center was not completely updated to reflect this, and the maximum value for the property was not modified. One consequence of this was that the maximum value for the property (which was 99999) actually meant 99999 milliseconds, not 99999 seconds. As a result, the maximum value for AMQPKA at V9.0 and V9.1 was about 100 seconds - when the property was defined as being in seconds in IBM MQ V8, the maximum value was about 28 hours. Another potential consequence was that the interval at which AMQP keep alive frames were sent by the MQ AMQP service across the network connection to a connected AMQP client was different than expected when setting the attribute value.
Problem conclusion
To resolve this issue, runmqsc and MQ Explorer have been updated so that the maximum allowed value for the channel attribute "AMQP keep alive" (AMQPKA) is now 99999999 milliseconds. This is very similiar to the maximum allowed value for the attribute in MQ V8, which is 99999 seconds In addition to this, the following topics in the IBM MQ V9.0.x and V9.1.x sections of IBM Knowledge Centre which mention the "AMQP Keep Alive" channel attribute have been updated to state that the property is set in milliseconds: v9.0: * ALTER CHANNEL (https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com .ibm.mq.ref.adm.doc/q085170_.htm) * Channel Properties (https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com .ibm.mq.explorer.doc/e_properties_channels.htm) * DEFINE CHANNEL (https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com .ibm.mq.ref.adm.doc/q085520_.htm) * DISPLAY CHANNEL (https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com .ibm.mq.ref.adm.doc/q086040_.htm) * DISPLAY CHSTATUS (https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.0.0/com .ibm.mq.ref.adm.doc/q086090_.htm) * Change, copy and create channel(https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9. 0.0/com.ibm.mq.ref.adm.doc/q086930_.htm) v9.1: * ALTER CHANNEL -- https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.1.0/com. ibm.mq.ref.adm.doc/q085170_.htm * Channel properties -- https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.1.0/com. ibm.mq.explorer.doc/e_properties_channels.htm * DEFINE CHANNEL -- https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.1.0/com. ibm.mq.ref.adm.doc/q085520_.htm * DISPLAY CHANNEL -- https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.1.0/com. ibm.mq.ref.adm.doc/q086040_.htm * DISPLAY CHSTATUS -- https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.1.0/com. ibm.mq.ref.adm.doc/q086090_.htm * Change, copy and create channel -- https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.1.0/com. ibm.mq.ref.adm.doc/q086930_.htm --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v9.0 LTS 9.0.0.9 v9.1 CD 9.1.5 v9.1 LTS 9.1.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 number
IT27173
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
2018-12-03
Closed date
2019-12-20
Last modified date
2019-12-20
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:
20 December 2019