PI26313: JOBS RUN WITH LAUNCH CLIENT INTERMITTENTLY FAIL WITH WSCL0912E C OMPONENT FAILED TO INITIALIZE

7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• Jobs run with launchClient intermittently fail with
  com.ibm.ws.exception.ConfigurationError: WSCL0912E component
  failed to initialize.
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  WebSphere Application Server users of       *
  *                  launchClient                                *
  ****************************************************************
  * PROBLEM DESCRIPTION: Invocations of launchClient             *
  *                      intermittently fail with                *
  *                      com.ibm.ws.exception.ConfigurationError *
  *                      : WSCL0912E                             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The messaging component failed to initialize due a problem
  installing the bundle for the WMQ Resource Adapter.  A typical
  partial call stack is shown below:
  JMSClientRegi 3   org.osgi.framework.BundleException: Error
  converting plugin at
  /n01/data/wbh/70x/profiles/Dmgr01/configuration/org.eclipse.osgi
  /bundles/135/1/bundlefile.
  at
  org.eclipse.core.runtime.internal.adaptor.EclipseStorageHook.gen
  erateManifest(EclipseStorageHook.java:334)
  at
  org.eclipse.core.runtime.internal.adaptor.EclipseStorageHook.get
  GeneratedManifest(EclipseStorageHook.java:311)
  at
  org.eclipse.core.runtime.internal.adaptor.EclipseStorageHook.cre
  ateCachedManifest(EclipseStorageHook.java:290)
  at
  org.eclipse.core.runtime.internal.adaptor.EclipseStorageHook.get
  Manifest(EclipseStorageHook.java:395)
  at
  org.eclipse.osgi.internal.baseadaptor.BaseStorage.loadManifest(B
  aseStorage.java:241)
  at
  org.eclipse.osgi.internal.baseadaptor.BundleInstall.begin(Bundle
  Install.java:82)
  at
  org.eclipse.osgi.framework.internal.core.Framework.installWorker
  Privileged(Framework.java:823)
  at
  org.eclipse.osgi.framework.internal.core.Framework$2.run(Framewo
  rk.java:739)
  at
  java.security.AccessController.doPrivileged(AccessController.jav
  a:327)
  at
  org.eclipse.osgi.framework.internal.core.Framework.installWorker
  (Framework.java:790)
  at
  org.eclipse.osgi.framework.internal.core.Framework.installBundle
  (Framework.java:734)
  at
  org.eclipse.osgi.framework.internal.core.BundleContextImpl.insta
  llBundle(BundleContextImpl.java:221)
  at
  com.ibm.ejs.jms.JMSRegistrationHelper.installBundle(JMSRegistrat
  ionHelper.java:551)
  ...
  

Problem conclusion

• APAR PM80934 introduced a WebSphere variable
  MQ_USE_BUNDLE_REFERENCE_INSTALL to address this issue, however
  the variable is not accessible in a launchClient environment.
  
  The messaging component was modified so that the function
  enabled in APAR PM80934 can be enabled in the client
  environment by specifying a JVM
  system property with name MQ_USE_BUNDLE_REFERENCE_INSTALL
  with a value of true.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 7.0.0.37, 8.0.0.11 and 8.5.5.5.  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 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

• R700 PSY

     UP

• R800 PSY

     UP

• R850 PSY

     UP