IBM Support

PM53083: WEBSPHERE APPLICATION SERVER SIBMQLINKSENDERCHANNEL AND SIBMQLINKRECEIVERCHANNEL MBEANS DO NOT EMIT NOTIFICATIONS

Fixes are available

8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • WebSphere Application Server with default message provider
    configured with MQLink. When SIBMQLinkSender Channel and
    SIBMQLinkReceiverChannel MBeans are started and stopped, they
    do not emit notifications.
    

Local fix

  • Use SIBMQLink MBean instead of SIBMQLinkSenderChannel and
    SIBMQLinkReceiverChannel MBeans
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the default messaging provider     *
    *                  for IBM WebSphere Application Server        *
    *                  version 7.0 and 8.0.                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: Missing notifications during            *
    *                      SIBMQLinkSenderChannel and              *
    *                      SIBMQLinkReceiverChannel start or       *
    *                      stop.                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Runtime event listeners for all MQLinkSenderChannel and
    MQLinkReceiverChannel notifications were registered via
    managed bean (MBean) type MQLink instead of  MBean type
    SIBMQLinkSenderChannel and SIBMQLinkReceiverChannel.
    So a JMX client could not receive Sender and Receiver Channel
    notifications if it registered for SIBMQLinkSenderChannel
    or SIBMQLinkReceiverChannel MBean type notifications. JMX
    client could receive Sender and Receiver Channel notifications
    only if it registered for MQLink MBean type notifications.
    

Problem conclusion

  • Source code has been modified to register runtime event
    listeners for MQLinkSenderChannel and MQLinkReceiverChannel
    notifications via MBean type SIBMQLinkSenderChannel and
    SIBMQLinkReceiverChannel.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.25 and 8.0.0.5.  Please refer to the
    Recommended  Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • If the JMX client expects MQLinkSenderChannel or
    ReceiverChannel notifications, do not register
    notification listeners for SIBMQLinkSenderChannel MBean
    notifictions.
    
    Register your JMX client to listen only for MQLink
    notifications.
    

Comments

APAR Information

  • APAR number

    PM53083

  • Reported component name

    PLAT MSG COM

  • Reported component ID

    620600101

  • Reported release

    200

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-11-29

  • Closed date

    2012-04-16

  • Last modified date

    2012-11-06

  • 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

    PLAT MSG COM

  • Fixed component ID

    620600101

Applicable component levels

  • R200 PSY

       UP



Document information

More support for: WebSphere Application Server
Service Integration Technology

Software version: 6.1

Reference #: PM53083

Modified date: 06 November 2012