IBM Support

IT15590: WINDOWS DATAFLOWENGINE PROCESS CAN HANG FOREVER ON SHUTDOWN

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

  • When an integration server is configured for callable flows or
    secure connectivity (for IBM Integration Bus on Cloud), that
    integration server may hang forever on shutdown on certain
    versions of Windows.
    
    If this happens, then the integration server will log a BIP2204I
    message to the event viewer stating that it has stopped, but the
    integration node will later report a BIP2804E indicating that it
    has not shut down.
    
    The problem has been seen on Windows 7, but not later versions
    of Windows.  On Windows 7, inspection of the hung
    DataFlowEngine.exe process using a tool such as Process
    Explorer shows the following stack:
    
    ntoskrnl.exe!KeWaitForMultipleObjects+0xc0a
    ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x712
    ntoskrnl.exe!KeWaitForMutexObject+0x19f
    ntoskrnl.exe!PoStartNextPowerIrp+0xbb4
    ntoskrnl.exe!PoStartNextPowerIrp+0x185d
    ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x91d
    ntoskrnl.exe!KeWaitForMutexObject+0x19f
    ntoskrnl.exe!ExQueryAttributeInformation+0x73a
    ntoskrnl.exe!KeSynchronizeExecution+0x3a23
    ntdll.dll!ZwReleaseKeyedEvent+0xa
    ntdll.dll!EtwEventSetInformation+0x3f40
    CommonServices.dll!ImbThreadPoolExecutor::?ImbThreadPoolExecutor
    +0x6b
    CommonServices.dll!stl_debug_terminate+0x47b8a
    CommonServices.dll!stl_debug_terminate+0x694
    CommonServices.dll!stl_debug_terminate+0x916
    ntdll.dll!LdrShutdownProcess+0x1d1
    ntdll.dll!RtlExitUserProcess+0x90
    mscoreei.dll!ND_WU1+0x18a
    mscoree.dll!CorExitProcess+0x10d
    MSVCR120.dll!_setusermatherr+0x2ab
    MSVCR120.dll!initterm_e+0x212
    DataFlowEngine.exe!ImbMain::operator=+0x2a02
    kernel32.dll!BaseThreadInitThunk+0xd
    ntdll.dll!RtlUserThreadStart+0x21
    
    The process can be killed by using the Task Manager or a tool
    such as Process Explorer.
    

Local fix

  • The dataflowengine process can be killed by using the Task
    Manager or a tool such as Process Explorer.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus V10.0.0.5 on Windows.
    
    
    Platforms affected:
    Windows on x86-64 platform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When an integration server is configured for callable flows or
    secure connectivity (for IBM Integration Bus on Cloud), that
    integration server may hang forever on shutdown on certain
    versions of Windows.
    
    If this happens, then the integration server will log a BIP2204I
    message to the event viewer stating that it has stopped, but the
    integration node will later report a BIP2804E indicating that it
    has not shut down.
    
    The problem has been seen on Windows 7, but not later versions
    of Windows. On Windows 7, inspection of the hung
    DataFlowEngine.exe process using a tool such as Process Explorer
    shows the following stack:
    
    ntoskrnl.exe!KeWaitForMultipleObjects+0xc0a
    ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x712
    ntoskrnl.exe!KeWaitForMutexObject+0x19f
    ntoskrnl.exe!PoStartNextPowerIrp+0xbb4
    ntoskrnl.exe!PoStartNextPowerIrp+0x185d
    ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x91d
    ntoskrnl.exe!KeWaitForMutexObject+0x19f
    ntoskrnl.exe!ExQueryAttributeInformation+0x73a
    ntoskrnl.exe!KeSynchronizeExecution+0x3a23
    ntdll.dll!ZwReleaseKeyedEvent+0xa
    ntdll.dll!EtwEventSetInformation+0x3f40
    CommonServices.dll!ImbThreadPoolExecutor::?ImbThreadPoolExecutor
    +0x6b
    CommonServices.dll!stl_debug_terminate+0x47b8a
    CommonServices.dll!stl_debug_terminate+0x694
    CommonServices.dll!stl_debug_terminate+0x916
    ntdll.dll!LdrShutdownProcess+0x1d1
    ntdll.dll!RtlExitUserProcess+0x90
    mscoreei.dll!ND_WU1+0x18a
    mscoree.dll!CorExitProcess+0x10d
    MSVCR120.dll!_setusermatherr+0x2ab
    MSVCR120.dll!initterm_e+0x212
    DataFlowEngine.exe!ImbMain::operator=+0x2a02
    kernel32.dll!BaseThreadInitThunk+0xd
    ntdll.dll!RtlUserThreadStart+0x21
    
    The process can be killed by using the Task Manager or a tool
    such as Process Explorer.
    
    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

    IT15590

  • 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-06-08

  • Closed date

    2016-08-25

  • Last modified date

    2016-08-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

[{"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":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 March 2020