IBM Support

PH22740: OSGI APPLICATION FAILS TO START IN AZURE ENVIRONMENT

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

  • OSGI application fails to start in Azure environment.
    
    [2/13/20 11:09:41:734 EST] 00000081 CompositionUn A  WSVR0190I:
    Starting composition unit
    WebSphere:cuname=com.ibm.mdm.hub.server.app-E001_0001.eba in BLA
     WebSphere:blaname=MDM-operational-server-EBA-E001.
    
    
    [2/13/20 11:10:06:547 EST] 00000081 CompositionUn E  WSVR0194E:
    Composition unit
    WebSphere:cuname=com.ibm.mdm.hub.server.app-E001_0001.eba in BLA
    WebSphere:blaname=MDM-operational-server-EBA-E001 failed to
    start.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  WebSphere Application Server users of OSGi  *
    *                  applications                                *
    ****************************************************************
    * PROBLEM DESCRIPTION: OSGi application fails to start.        *
    *                      Messages WSVR0194E and CWSAI0049E are   *
    *                      generated in the logs.                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When an OSGi application is started, the Aries integration
    layer waited for up to ten seconds for required services, such
    as the Bundle Framework Manager, to start.  In some
    environments it is possible that these services will not
    become available within the time limit.
    

Problem conclusion

  • The default time limit to wait for required services to become
    available during OSGi application startup was modified to a
    default of 60 seconds.
    In addition a new JVM System Property,
    com.ibm.websphere.AriesApplicationEventHandler.trackerTimeout
    , can be used to specify the timeout value in milliseconds.
    
    The fix for this APAR is targeted for inclusion in fix pack
    9.0.5.8. For more information, see 'Recommended Updates for
    WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH22740

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-02-28

  • Closed date

    2021-05-11

  • Last modified date

    2021-05-11

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900"}]

Document Information

Modified date:
12 May 2021