IBM Support

IT27173: AMQPKA attribute incorrectly shown as being in seconds

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

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

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