IBM Support

IT21072: JMS NODES ARE SLOW TO OBTAIN A CONECTION FROM A CONNECTION FACTORY WHEN A DIFFERENT FACTORY HAS A CONNECTION FAILURE

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

  • A JMS node is failing to get a JMS Connection because of a
    network outage
    with the a JMS server. The JMS provider's client takes a long
    time to respond
    to the connection request from the JMS node.
    
    This can cause a long delay obtaining a second JMS Connection in
    another JMS
    node which uses a different JMS server.
    
    The second JMS node is in a message flow deployed to the same
    Integration Server
    as the first JMS node.
    
    
    
    Additional Symptom(s) Search Keyword(s):
    JMS,Connection,Delay,Reconnect
    

Local fix

  • Restart or reload the Integration Server.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus V9.0 and higher using JMS
    Nodes.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    JMS connections are stored in an internal cache in each
    Integration Server for reuse.
    This cache uses a locking mechanism to ensure the integrity of
    each JMS connection
    in the cache.
    
    A delayed response from a JMS server to a JMS node when
    obtaining a new JMS
    Connection holds the lock on the JMS Connection cache. This can
    prevent other
    JMS nodes from retrieving their cached JMS Connections.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT21072

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0530

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-06-18

  • Closed date

    2018-03-21

  • Last modified date

    2018-03-21

  • 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

    5724J0530

Applicable component levels

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

Document Information

Modified date:
23 March 2020