IBM Support

IV73699: AFTER A REFRESH SECURITY TYPE(SSL) COMMAND, MESSAGES CANNOT BE PROCESSED USING SSL ENABLED CLUSTER CHANNELS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After a REFRESH SECURITY TYPE(SSL) command, messages cannot be
    processed using SSL enabled cluster channels.
    The problem is that there is a channel status inconsistency
    present between "display chs" runmqsc output and the channel
    status saved
    in the cluster cache.
    
    Display channel status shows the channel as running:
    AMQ8417: Display Channel Status details.
    CHANNEL(TO.QM1) CHLTYPE(CLUSRCVR
    RQMNAME(QM2) STATUS(RUNNING)
    
    Cluster cache shows:
    Qm(QM1) Live Seq(1425992591)
    Channel(TO.QM1 ) Stopping
    
    Cluster cache dump can be obtained by running an amqrfdm
    command:
    http://www-01.ibm.com/support/docview.wss?uid=swg21293315
    See step 2 - Collecting Data
    Point 3 - Collecting data manually
    

Local fix

  • Restart cluster channels
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users issuing a REFRESH SECURITY TYPE(SSL) command and
    subsequently putting messages to a cluster queue with a local
    instance.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The processing of this command includes the local CLUSRCVR
    channel being stopped. The cluster cache status of the queue
    manager incorrectly remained as STOPPING instead of being set to
    INACTIVE.
    This meant that messages put to a clustered queue on the local
    queue manager and on other queue managers in the cluster were
    not workload balanced to the local queue instance, since the
    STOPPING status has lower priority than INACTIVE or RUNNING.
    

Problem conclusion

  • The MQ queue manager logic has been updated to correctly modify
    the cluster cache status to INACTIVE when stopping a CLUSRCVR
    channel.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.0       7.0.1.14
    v7.1       7.1.0.7
    v7.5       7.5.0.6
    v8.0       8.0.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

    IV73699

  • Reported component name

    WMQ LIN X86 V7

  • Reported component ID

    5724H7224

  • Reported release

    701

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-05-29

  • Closed date

    2015-08-18

  • Last modified date

    2015-11-13

  • 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 LIN X86 V7

  • Fixed component ID

    5724H7224

Applicable component levels

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1"}]

Document Information

Modified date:
08 March 2021