IBM Support

IT16296: JMSINPUT NODE FOR DURABLE SUBSCRIPTION CAN CREATE MULTIPLE MQ SUBSCRIPTIONS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If JMSInput nodes are configured for durable subscriptions with
    the same ConnectionFactory and are deployed as part of multiple
    message flows with the same name inside different applications,
    then multiple subscriptions can get created for each JMSInput
    node. During re-deploy or restart of the message flow a new
    subscription can get created for the JMSInput node with a
    different subscription name.
    
    
    
    Additional Symptom(s) Search Keyword(s): JMSInput, Durable
    subscription
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus using the JMSInput node for
    durable subscriptions.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If JMSInput nodes are configured for durable subscriptions with
    the same ConnectionFactory and are deployed as part of message
    flows of the same name inside different applications, then
    multiple subscriptions can get created for each JMSInput node.
    During re-deploy or restart of the message flow a new
    subscription can get created for the JMSInput node with a
    different subscription name in the JMSProvider .
    
    There are a number of resource name changes between WebSphere
    Message Broker and IBM Integration Bus Version 9.0.  For details
    visit
    http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e
    tools.mft.doc/bb23814_.htm
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT16296

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-07-26

  • Closed date

    2017-05-25

  • Last modified date

    2017-05-25

  • 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

    INTEGRATION BUS

  • Fixed component ID

    5724J0540

Applicable component levels

  • RA00 PSY

       UP

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0"}]

Document Information

Modified date:
10 September 2020