IBM Support

IT31305: BIPSERVICE TERMINATES AFTER STARTING BIPBROKER IF UNABLE TO UPDATE REGISTRY WITH PID

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 the bipservice process detects that the bipbroker process
    (Integration Node) has terminated unexpectedly, it will restart
    the process and update the registry with the new process ID. If
    the registry file update fails, for example if the file system
    is full due to a large core file having been created, then the
    bipservice process terminates leaving an orphaned bipbroker.
    
    Additional Symptom(s) Search Keyword(s):
    

Local fix

  • NA
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus V10 and IBM App Connect
    Enterprise V11.
    
    
    Platforms affected:
    z/OS, MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The bipservice process is the first process that is started when
    starting an Integration Node. It will start and monitor the
    bipbroker (AdminAgent) process. If the bipservice process
    detects that the bipbroker process has terminated unexpectedly,
    it will restart the process and update the registry with the new
    process ID. If the registry file update fails, for example if
    the file system is full, the exception is not handled and the
    bipservice process terminates leaving an orphaned bipbroker.
    

Problem conclusion

  • The bipbroker now catches the exception if the registry update
    fails, logs a BIP2110E error, and continues. The user should
    review the error and take the appropriate action.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.20
    v11.0      11.0.0.8
    
    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

    IT31305

  • 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

    2019-12-16

  • Closed date

    2020-04-09

  • Last modified date

    2020-04-09

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

Document Information

Modified date:
09 April 2020