IBM Support

IT26167: MAX IAPI CLIENT LIMIT REACHED WHEN BROKEN NAMED PIPE NOT HANDLEDON WINDOWS

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

  • Additional Symptom(s) Search Keyword(s):
    A message flow running on Windows that calls the Integration
    API (IAPI) getConfigurableService() to access a "UserDefined"
    configurable service fails after 100 requests, even though the
    message flow calls disconnect() on the BroxyProxy object after
    each request. The default limit on concurrent local IAPI client
    connections is 100.
    The problem is that the Integration Node is not handling a
    broken named pipe correctly when the message flow disconnects
    such that the BrokerProxy object is not being successfully
    deregistered.
    
    The following error might be seen in a trace:
    BIP2112E: Integration node internal error: diagnostic
    information 'Could not launch a handler for a local CMP
    connection'
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus V10 and IBM App Connect
    Enterprise V11 on Windows.
    
    
    Platforms affected:
    Windows on x86-64 platform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A message flow running on Windows that calls the Integration API
    (IAPI) getConfigurableService() to access a "UserDefined"
    configurable service fails after 100 requests, even though the
    message flow calls disconnect() on the BrokerProxy object after
    each request. The default limit on concurrent local IAPI client
    connections is 100.
    The problem is that the Integration Node is not handling a
    broken named pipe correctly when the message flow disconnects
    such that the BrokerProxy object is not being successfully
    deregistered.
    
    The following error might be seen in a trace:
    BIP2112E: Integration node internal error: diagnostic
    information 'Could not launch a handler for a local CMP
    connection'
    

Problem conclusion

  • The product now correctly handles the return code from reading a
    named pipe that indicates that the pipe is broken.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.15
    v11.0      11.0.0.2
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT26167

  • 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

    2018-09-03

  • Closed date

    2018-10-11

  • Last modified date

    2018-10-11

  • 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

[{"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":"10.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
11 October 2018