IBM Support

IT34424: BIP2044W WRITTEN TO EVENT LOG EVERY 60 SECONDS FOR HA NODE ON WINDOWS

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

  • With IBM App Connect Enterprise 11.0.0.10, an integration node
    on Windows that has been created with a shared work path (-e |
    --shared-workpath) and a non-default local work path (-w |
    --workpath) will write the following warning message to the
    Windows Event Log every 60 seconds on startup:
    
    BIP2044W The
    integration server ''serverName'' (process-id '12345') is still
    starting after xx seconds.
    
    The integration server process is
    taking longer than usual to startup. This message will be
    repeated until the integration server starts.
    
    The integration
    server has actually started successfully but the integration
    node is not detecting that the process is running.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM App Connect Enterprise V11 on Windows using an
    HA shared work path and a non-default local workpath.
    
    
    Platforms affected:
    Windows on x86-64 platform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    With IBM App Connect Enterprise 11.0.0.10, an integration node
    on Windows that has been created with a shared work path ( -e |
    --shared-workpath ) and a non-default local work path ( -w |
    --workpath) will write the following warning message to the
    Windows Event Log every 60 seconds on startup:
    
    BIP2044W The integration server ''serverName'' (process-id
    '12345') is still starting after xx seconds. The integration
    server process is taking longer than usual to startup. This
    message will be repeated until the integration server starts.
    
    The integration server has actually started successfully but the
    integration node is not detecting that the process is running.
    This is because the file containing the process ID of the
    integration server is not in the expected location on the file
    system.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT34424

  • Reported component name

    APP CONNECT ENT

  • Reported component ID

    5724J0550

  • Reported release

    B00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-10-02

  • Closed date

    2020-12-15

  • Last modified date

    2020-12-15

  • 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

    APP CONNECT ENT

  • Fixed component ID

    5724J0550

Applicable component levels

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00"}]

Document Information

Modified date:
16 December 2020