IBM Support

PH19730: LAUNCHCLIENT JOBS FAILED WITH ERROR MESSAGE WSCL0912E "COMPONENT FAILED TO INITIALIZE"

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

  • When executing jobs using launchClient, sometimes the job
    failed with below error:
    
    [1/24/19 21:05:32:273 PST] 00000001 3
    UOW= source=com.ibm.ws.client.applicationclient.launchClient
    org=IBM prod=WebSphere component=Application Server thread=[P=71
    7950:O=0:CT]
    com.ibm.websphere.client.applicationclient.ClientContainerExcept
    ion: com.ibm.ws.exception.ConfigurationError:
    WSCL0912E: Component failed to initialize.
    at
    com.ibm.ws.client.applicationclient.ClientContainer.initializeCo
    mponents(ClientContainer.java:1926)
    at
    com.ibm.ws.client.applicationclient.ClientContainer.init(ClientC
    ontainer.java:321)
    at
    com.ibm.ws.client.applicationclient.launchClient.createContainer
    AndLaunchApp(launchClient.java:749)
    at
    com.ibm.ws.client.applicationclient.launchClient.main(launchClie
    nt.java:495)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
    Impl.java:95)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
    AccessorImpl.java:56)
    ...
    Caused by:
    com.ibm.ws.exception.ConfigurationError: WSCL0912E: Component
    failed to initialize.
    at
    com.ibm.ws.client.applicationclient.ClientComponentInitImpl.init
    ializeComponents(ClientComponentInitImpl.java:124)
    at
    com.ibm.ws.client.applicationclient.ClientComponentInitImpl.init
    ialize(ClientComponentInitImpl.java:67)
    at
    com.ibm.ws.client.applicationclient.ClientContainer.initializeCo
    mponents(ClientContainer.java:1919)
    ....
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Application executed with               *
    *                      launchClient tool fails with            *
    *                      WSCL0912E when executing multiple       *
    *                      clients simultaneously.                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a JavaEE Application Client is executed using the
    launchClient tool the Messaging component converts the
    WebSphere MQ application adapter to an OSGi bundle and
    performs consistency checks with any pre-existing OSGi bundle
    in the OSGi cache.  The OSGi cache may be used by multiple
    client processes concurrently, but the OSGi platform does
    not provide a multi-process safe way of interacting with the
    OSGi cache concurrently.  Setting the JVM System Property
    MQ_USE_BUNDLE_REFERENCE_INSTALL to a value of true would
    normally resolve this issue but was not possible in this
    particular case.
    Typically the first client would initialize the bundle in the
    OSGi cache and this would be reused by futher client
    invocations however, when using non-standard OSGi environment
    variables eg osgi.configuration.area.readOnly=true this does
    not occur and simultaneous execution of multiple launchClient
    processes can result in a
    org.eclipse.osgi.service.pluginconversion.PluginConversionExcept
    ion.  This causes initialization of the Messaging component to
    fail resulting in the "WSCL0912E: Component failed to
    initialize." message being generated and the termination of
    the launchClient process.
    

Problem conclusion

  • The issue can normally be resolved by setting the
    MQ_USE_BUNDLE_REFERENCE_INSTALL JVM System Property to true.
    
    In cases where this is not possible a separate mechanism has
    been provided that makes use of file locking to synchronize
    the concurrent launchClient processes around the Messaging
    component's use of the OSGi Cache during initialization.
    
    To specify the use of the alternate mechanism the following
    JVM System Properties can be specified:
    
    MQ_CLIENT_USE_FILE_LOCKING
    values:
    force - file locking is used to synchronize multiple
    launchClient processes running on the node.  If there are any
    issues locking the file the Messaging component initialization
    fails.
    true - file locking is used to synchronize multiple
    launchClient processes running on the node, however if there
    are any issues accessing the locking file the Messaging
    component initialization continues without locking.
    
    NOTE issues in this case would include permissions
    problems creating or accessing the locking file and would NOT
    include the file being already locked (in which case the
    process waits for the lock, which is generally short-lived).
    
    default - unset, file locking not in use, no change in
    behaviour
    
    MQ_CLIENT_FILE_LOCKING_DIR
    values:
    The directory in which to create the locking file.
    default - unset, will use value of User Home Directory (as set
    in JVM System Property user.home).
    
    NOTE if MQ_CLIENT_USE_FILE_LOCKING is not specified then any
    value set in MQ_CLIENT_FILE_LOCKING_DIR is ignored and locking
    is not used.
    
    NOTE JVM System Properties can be specified on the
    launchClient command using -CCD<System_Prop_Name>=<value> for
    example:
    
    launchClient myClientApp.ear
    -CCBootstrapHost=mywasserver.mycompany.com
    -CCDMQ_CLIENT_USE_FILE_LOCKING=force
    -CCDMQ_CLIENT_FILE_LOCKING_DIR=\batchClientLockDir
    
    
    
    The fix for this APAR is targeted for inclusion in fix packs
    8.5.5.18 and 9.0.5.5. 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

    PH19730

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-11-27

  • Closed date

    2020-09-02

  • Last modified date

    2020-09-02

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

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":"850"}]

Document Information

Modified date:
14 September 2020