IBM Support

IT34856: HIGH CPU USAGE ON WINDOWS IF A NAMED PIPE BECOMES INVALID WHILE IT IS BEING WRITTEN TO

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

  • The product uses Windows named pipes for inter-process
    communication. If a named pipe becomes invalid, for any reason,
    while a thread is attempting to write data to the pipe then
    that thread will get stuck in a loop. This thread will never
    exit and will consume a large amount of CPU.
    
    A service trace
    will show the thread stuck in the function ImbNamedPipe::send
    whereas a stack trace will show the same thread stuck in the
    function ImbNamedPipe::sendTimeout.
    

Local fix

  • N/A
    

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:
    The product uses Windows named pipes for inter-process
    communication. If a named pipe becomes invalid, for any reason,
    while a thread is attempting to write data to the pipe then that
    thread will get stuck in a loop. This thread will never exit and
    will consume a large amount of CPU.
    
    A service trace will show the thread stuck in the function
    ImbNamedPipe::send whereas a stack trace will show the same
    thread stuck in the function ImbNamedPipe::sendTimeout.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT34856

  • 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

    2020-11-10

  • Closed date

    2020-12-15

  • Last modified date

    2020-12-15

  • 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

[{"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:
16 December 2020