IBM Support

IT22683: INTEGRATION NODE ABEND ON STARTUP DUE TO CORRUPT HA LOCK FILE

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

  • An integration node configured for high availability may abend
    on startup if the HA lock file repository_ha_active.lock in
    directory
    <HASharedWorkPath>/components/<integrationNodeName>/repository
    has become corrupted.
    
    The system log reports the BIP2001I message for the IBM
    Integration Bus service process starting, but this is then
    followed by repeated BIP2228E error messages to indicate that
    the agent process has abended. The abend files contain no stack
    information.
    
    A service trace of the agent process starting shows the
    following entries immediately prior to the abend:
    
      ImbConfigStore::obtainHALock  'Obtained the HA repository lock
    and the file handle is '
      ImbConfigStore::obtainHALock  'The HA lock count now = ' , 1
    } ImbConfigStore::obtainHALock
    
    The lock file should only contain the host name of the
    integration node that holds the lock, but the file size is
    reported as being unusually large (greater than 1024 bytes).
    

Local fix

  • Remove the lock file and restart the integration node.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus V9.0 and V10.0 using
    integration nodes configured for high availability.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    An integration node configured for high availability may abend
    on startup if the HA lock file repository_ha_active.lock in
    directory
    <HASharedWorkPath>/components/<integrationNodeName>/repository
    has become corrupted.
    
    The system log reports the BIP2001I message for the IBM
    Integration Bus service process starting, but this is then
    followed by repeated BIP2228E error messages to indicate that
    the agent process has abended. The abend files contain no stack
    information.
    
    A service trace of the agent process starting shows the
    following entries immediately prior to the abend:
    
      ImbConfigStore::obtainHALock  'Obtained the HA repository lock
    and the file handle is '
      ImbConfigStore::obtainHALock  'The HA lock count now = ' , 1
    } ImbConfigStore::obtainHALock
    
    The lock file should only contain the host name of the
    integration node that holds the lock, but the file size is
    reported as being unusually large (greater than 1024 bytes). The
    file still contains the correct host name information, but the
    file size returned is being used on a re-write operation. If the
    file size is greater than 1024 bytes, storage corruption occurs.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT22683

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0530

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-10-05

  • Closed date

    2017-11-28

  • Last modified date

    2017-11-28

  • 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

    5724J0530

Applicable component levels

  • R900 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":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 November 2017