PK76300: IBM CLIENT FOR JMS ON J2SE WITH IBM WEBSPHERE APPLICATION SERVER DOES NOT WORK IF OSGI BOOT DELEGATION IS DISABLED

Fixes are available

APAR status

Closed as program error.

Error description

If you run the IBM Client for JMS on J2SE with IBM
WebSphere Application Server in an OSGi environment with
the osgi.compatibility.bootdelegation property set to
false, the client fails.
The error reported is either a ClassNotFoundException, or
a failure resolving OSGi dependencies.

Local fix

Correct the jar so that they do import/export in OSGi
environments.

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the IBM Client for JMS on J2SE     *
*                  with IBM WebSphere Application Server, or   *
*                  the standalone JMS client for WebSphere     *
*                  Application Server V7.0, in an OSGi         *
*                  environment                                 *
****************************************************************
* PROBLEM DESCRIPTION: If the OSGi environment has the         *
*                      osgi.compatibility.bootdelegation       *
*                      Java property set to                    *
*                      false, an application attempting        *
*                      to use the JMS client fails.            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Setting the osgi.compatibility.bootdelegation
system property to false enforces OSGI restrictions that
prevent the JMS client from accessing classes it requires
within the class library of the virtual machine. This is
because the JMS client does not state dependencies on these
packages in its manifest.
This either results in ClassNotFoundException exceptions or a
failure to resolve OSGi bundle dependencies.

Problem conclusion

The IBM Client for JMS on J2SE with IBM WebSphere Application
Server, and the standalone client for JMS in WebSphere
Application Server V7.0, are updated to declare
additional bundle dependencies and exports.

With this APAR applied, the JMS client can be used in an
OSGi environment where osgi.compatibility.bootdelegation is set
to false.

Application plug-ins using these standalone JMS clients should
import the following packages:
javax.jms
If using pragmatically created connection factories then the
following package should also be imported by
the application plug-in:
com.ibm.websphere.sib.api.jms
Alternatively, if using JNDI lookups then the following
packages should also be imported by the application
plug-in:
com.ibm.websphere.naming

If JNDI lookups are used, it is necessary to set the following
system property:
- For the IBM Client for JMS on J2SE with IBM WebSphere
Application Server:
org.osgi.framework.system.packages=
com.ibm.CORBA.iiop,
<all packages exported by system.bundle>
- For the JMS standalone client for WebSphere Application
Server V7.0:
org.osgi.framework.system.packages=
sun.io,com.ibm.wsspi.channel.framework,
com.ibm.CORBA.channel,
com.ibm.CORBA.channel.giop,com.ibm.channel.orb,
com.ibm.CORBA.poa,
com.ibm.CORBA.ras,
com.ibm.CORBA.iiop,
com.ibm.CORBA.transport,
<all packages exported by system.bundle>

A list of all packages exported by system.bundle can be
obtained from the Execution Environment Profile being
used. If the Execution Environment is say J2SE-1.4 then the
list of all packages exported by system.bundle can
be obtained from the property
org.osgi.framework.system.packages in the Execution
Environment Profile file named J2SE-1.4.profile contained in
the bundle org.eclipse.osgi_<version>.jar

Temporary fix

Comments

APAR Information

APAR number
PK76300
Reported component name
PLAT MSG COM
Reported component ID
620400101
Reported release
100
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-11-24
Closed date
2009-01-20
Last modified date
2009-01-20

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
PLAT MSG COM
Fixed component ID
620400101

Applicable component levels

R100 PSY
UP

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

Document Information

Modified date:
23 October 2021

Tips

PK76300: IBM CLIENT FOR JMS ON J2SE WITH IBM WEBSPHERE APPLICATION SERVER DOES NOT WORK IF OSGI BOOT DELEGATION IS DISABLED

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

R100 PSY

Document Information

Share your feedback

Need support?