IBM Support

PI58640: EXCEPTION WSCL0912E : COMPONENT COULD NOT BE INITIALIZED RUNNING LAUNCHCLIENT ON MICROSOFT WINDOWS.

Fixes are available

9.0.0.1: WebSphere Application Server traditional V9.0 Fix Pack 1
9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
9.0.5.6: WebSphere Application Server traditional Version 9.0.5 Fix Pack 6

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customer is getting exception
    com.ibm.ws.exception.ConfigurationError : WSCL0912E : Component
    could not be initialized.
    
    FFDC generated will have a call stack as below (partial stack sh
    
    [21/07/16 11:11:52:902 BST]     FFDC Exception:org.eclipse.osgi.
    org.eclipse.osgi.framework.internal.core.Framework$DuplicateBund
     at org.eclipse.osgi.framework.internal.core.Framework.createAnd
     at org.eclipse.osgi.framework.internal.core.Framework.installWo
     at org.eclipse.osgi.framework.internal.core.Framework$1.run(Fra
     at java.security.AccessController.doPrivileged(AccessController
     at org.eclipse.osgi.framework.internal.core.Framework.installWo
     at org.eclipse.osgi.framework.internal.core.Framework.installBu
     at org.eclipse.osgi.framework.internal.core.BundleContextImpl.i
     at com.ibm.ejs.jms.JMSRegistrationHelper.installBundle(JMSRegis
    ...
    

Local fix

  • Make WAS_HOME environment variable identical (including
    upper/lower case) between the launchClient executions.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  WebSphere Application Server users of       *
    *                  launchClient on Windows platforms.          *
    ****************************************************************
    * PROBLEM DESCRIPTION: WSCL0912E : COMPONENT COULD NOT BE      *
    *                      INITIALIZED RUNNING LAUNCHCLIENT ON     *
    *                      WINDOWS.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The filesystem on Windows is case insensitive.  The problem
    occurs when the WAS_HOME environment variable for different
    launchClients is set to values that differ but only in case.
    When this occurs the messaging component attempts to install the
    WMQ Resource Adapter as an OSGi bundle with a bundle location
    that does not match the bundle location of the existing
    reference bundle causing the OSGi framework to throw a
    Framework$DuplicateBundleException.
    

Problem conclusion

  • The messaging component was modified to take into account the
    case-insensitivity of the Windows platform when installing the
    OSGi bundle for the WMQ Resource Adapter.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.5.5.11 and 9.0.0.2.  Please refer to the Recommended
    Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI58640

  • 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

    2016-03-07

  • Closed date

    2016-07-21

  • Last modified date

    2016-08-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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R850 PSY

       UP

  • R900 PSY

       UP

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

Document Information

Modified date:
15 October 2021