IBM Support

IT33614: HIGH CPU USAGE BY THE DATAFLOWENGINE PROCESS AFTER MQSISTOPMSGFLOW COMMAND TIMEOUT WITH BIP2242E ERROR MESSAGE.

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

  • If a message flow with MQInput node is configured with
    additional instances and one of the message flow thread is hung
    then mqsistopmsgflow command fails with a BIP2242E error message
    in the broker syslog file. If another message flow thread is
    waiting for an input message then a high CPU usage is observed
    with the DataFlowEngine process after the BIP2242E error
    message.
    
    BIP2242E: Message flow 'MyMessageFlow' could not be reconfigured
    because it remained busy for longer than the timeout period of
    '300000'
    

Local fix

  • Use the command 'mqsistopmsgflow {node} -e {server} -f
    restartExecutionGroup' to prevent the high CPU usage.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM App Connect Enterprise V11.0 and IBM
    Integration Bus V10.0 using the MQInput node with additional
    instances.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If a message flow with MQInput node is configured with
    additional instances and one of the message flow thread is hung
    then mqsistopmsgflow command fails with a BIP2242E error. If
    another message flow thread is waiting for an input message then
    a high CPU usage is observed on the DataFlowEngine process after
    the BIP2242E error message.
    
    BIP2242E: Message flow 'MyMessageFlow' could not be reconfigured
    because it remained busy for longer than the timeout period of
    '300000'
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT33614

  • 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-07-20

  • Closed date

    2020-08-27

  • Last modified date

    2020-08-27

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

Document Information

Modified date:
28 August 2020