IBM Support

IT36555: AMQ9635 error message displays arbitrary characters at the end of the CipherSpec in the MQ queue manager error logs

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

  • When specifying a deprecated CipherSpec that has not been
    enabled, the queue manager's error logs will display an AMQ9635
    error message with garbage characters shown at the end of the
    CipherSpec.  For example:
    
    AMQ9635: Channel 'MY.CHL' did not specify a valid CipherSpec.
    
    EXPLANATION:
    Channel 'MY.CHL' specifies a value of
    'TLS_RSA_WITH_AES_128_CBC_SHA
    4^W4^B' for CipherSpec which is not valid to start a
    secure
    connection.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Any MQ user receiving an AMQ9635 error message.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The queue manager failed to specify the maximum length of a
    CipherSpec when printing one in the explanation section of an
    AMQ9635 message.  In some cases, this caused random extra
    characters to be printed at the end of the CipherSpecvalue  as
    in this example:
    
    AMQ9635: Channel 'MY.CHL' did not specify a valid CipherSpec.
    
    EXPLANATION:
    Channel 'MY.CHL' specifies a value of
    'TLS_RSA_WITH_AES_128_CBC_SHA 4^W4^B' for CipherSpec
    which is not valid to start a secure connection.
    

Problem conclusion

  • The queue manager has been updated to ensure that the maximum
    CipherSpec length of 32 (MQ_SSL_CIPHER_SPEC_LENGTH) is used when
    printing the AMQ9635 message, preventing random characters from
    appearing in the queue manager error logs and in trace files.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.1 LTS   9.1.0.15
    v9.2 LTS   9.2.0.10
    v9.3 LTS   9.3.0.5
    v9.x CD    9.3.3
    
    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

    IT36555

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7271

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-04-12

  • Closed date

    2023-02-27

  • Last modified date

    2023-02-27

  • 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 MP

  • Fixed component ID

    5724H7271

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 February 2023