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

Fixes are available

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 number
PI26313
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-09-23
Closed date
2014-12-10
Last modified date
2014-12-10

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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022

Tips

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

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?