IBM Support

IV72011: A WEBSPHERE APPLICATION SERVER LISTENER PORT FAILS TO CONSUME MESSAGES FROM WEBSPHERE MQ WHEN USING MESSAGE SELECTORS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A message-driven bean application, using a WebSphere Application
    Server Listener Port and a message selector, fails to receive
    any messages even though there are messages on the queue
    monitored by the Listener Port that match the selector.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects three categories of user:
    
    Category 1:
    -----------
    Users of:
    
    - The WebSphere Application Server V8.5 WebSphere MQ messaging
    provider
    
    who have message-driven bean applications that:
    
    - Have been deployed to use either Listener Ports, or Activation
    Specifications, that connect to WebSphere MQ using WebSphere MQ
    messaging provider migration mode.
    - And use message selectors.
    
    Category 2:
    -----------
    Users of:
    
    - The WebSphere MQ V7.1 Resource Adapter
    - The WebSphere MQ V7.5 Resource Adapter
    - The WebSphere MQ V8.0 Resource Adapter
    
    who have message-driven bean applications that:
    
    - Have been deployed to use an Activation Specification which
    connects to WebSphere MQ using WebSphere MQ messaging provider
    migration mode.
    - And use message selectors.
    
    Category 3:
    -----------
    Users of:
    
    - The WebSphere MQ V7.1 classes for JMS
    - The WebSphere MQ V7.5 classes for JMS
    - The WebSphere MQ V8.0 classes for JMS
    
    who have applications that:
    
    - Connect to WebSphere MQ using WebSphere MQ messaging provider
    migration mode.
    - And use MessageListeners that have been created with a message
    selector.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The WebSphere MQ classes for JMS maintain an internal flag for
    every JMS application that uses either:
    
    - JMS MessageListeners
    - Activation Specifications
    - WebSphere Application Server Listener Ports
    
    and connects to WebSphere MQ using WebSphere MQ messaging
    provider migration mode. The flag represents the state of the
    application. It is set to true when the application is in a
    position to receive messages, and false if the application has
    been stopped and is unable to process messages at the current
    time.
    
    When message selectors are being used, then the WebSphere MQ
    classes for JMS will check each message that arrives on the JMS
    Destination being monitored by the MessageListener, Activation
    Specification or Listener Port to see if it matches the selector
    specified by an application. If it does, then the WebSphere MQ
    classes for JMS look at the internal flag for the application,
    to check that it is in a position to receive the message - if
    the application is able to process the message, then it is
    removed from the Destination and delivered to the application
    for processing. If the internal flag is set to false, however,
    then the application is not able to process the message at the
    current time. In this situation, the message is left on the
    Destination.
    
    Due to an error in the WebSphere MQ classes for JMS, the
    internal flag was always set to false for applications that used
    message selectors. As a result, the WebSphere MQ classes for JMS
    would never attempt to deliver messages that matched a message
    selector to the application using that selector.
    

Problem conclusion

  • The WebSphere MQ classes for JMS have been updated to ensure
    that the internal flag representing the state of applications
    using message selectors is set to true when the application is
    in a position to receive messages, and false when the
    application has been stopped.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.1       7.1.0.8
    v7.5       7.5.0.6
    v8.0       8.0.0.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

    IV72011

  • Reported component name

    WMQ AIX V7

  • Reported component ID

    5724H7221

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-04-09

  • Closed date

    2015-05-25

  • Last modified date

    2015-11-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

    WMQ AIX V7

  • Fixed component ID

    5724H7221

Applicable component levels

  • R710 PSY

       UP

[{"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.1"}]

Document Information

Modified date:
09 March 2021