IBM Support

PI86447: DUPLICATE EXECUTION GROUP PROCESSES STARTED ON SLOW SYSTEM WHEN REPEATEDLY STARTING AND STOPPING EGS

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

  • In some circumstances on slow systems if execution groups are
    repeatedly being stopped and started then it's possible for
    multiple execution group processes to be started for the same
    execution group which then leads to a loop as the second
    execution groups shuts down with the following error and is
    then restarted:
    
     +BIP2112E (Msg 1/1) MQxxBRK EGx 0 MESSAGE BROKER INTERNAL
    ERROR:
     DIAGNOSTIC INFORMATION 'Failed to acquire execution group lock
    - duplicate execution group processes?',
    'ImbFile::WriteLock::WriteLock()
     reported 'Failed to acquire write lock on file' with values...
    ''Failed to acquire write lock on file''
    ''/u/wmqixx/broker/components/MQ10BRK/5
    xxxxxxx-yyyy-zzzz-aaaa-bbbbbbbbbbbb/.lock'' '112''.
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus V9.0.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    In some circumstances on slow systems, if execution groups are
    repeatedly being stopped and started, then it's possible for
    multiple execution group processes to be started for the same
    execution group. This leads to a loop as the second
    execution group shuts down with the following error and is
    then restarted:
    
    +BIP2112E (Msg 1/1) MQxxBRK EGx 0 MESSAGE BROKER INTERNAL
    ERROR:
    DIAGNOSTIC INFORMATION 'Failed to acquire execution group lock
    - duplicate execution group processes?',
    'ImbFile::WriteLock::WriteLock()
    reported 'Failed to acquire write lock on file' with values...
    ''Failed to acquire write lock on file''
    ''/u/wmqixx/broker/components/MQ10BRK/5
    xxxxxxx-yyyy-zzzz-aaaa-bbbbbbbbbbbb/.lock'' '112''.
    

Problem conclusion

  • The product has changed to improve control of execution group
    startup and stop to avoid duplicate execution group processes
    being started.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.0       9.0.0.11
    
    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

    PI86447

  • Reported component name

    WEB MB Z/OS

  • Reported component ID

    5697P4400

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-08-25

  • Closed date

    2018-06-13

  • Last modified date

    2018-06-13

  • 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

    WEB MB Z/OS

  • Fixed component ID

    5697P4400

Applicable component levels



Document information

More support for: WebSphere Message Broker

Software version: 8.0

Reference #: PI86447

Modified date: 13 June 2018


Translate this page: