APAR status
Closed as program error.
Error description
The below Exception is thrown when trying to start an application that uses the IBM MQ classes for Java OSGi Redistributable client: detailMessage "JMSCC0091: The provider factory for connection type 'com.ibm.msg.client.wmq' could not be loaded." linkedException CSIException detailMessage "A Messaging Provider component was not found." The connection is unable to be successfully established. Additionally, when using IBM MQ classes for Java to connect to a queue manager using the Java OSGi Redistributable client, the following Exception would be returned: java.lang.ClassNotFoundException: javax.transaction.xa.XAException not found by com.ibm.mq.osgi.allclient
Local fix
NA
Problem summary
**************************************************************** USERS AFFECTED: This issue affects users of: - The IBM MQ v8.0 OSGi bundle com.ibm.mq.osgi.allclient_<version_number>.jar who use IBM MQ classes for JMS to connect to a queue manager. And users of: - The IBM MQ v8.0 OSGi bundle com.ibm.mq.osgi.allclient_<version_number>.jar - The IBM MQ v9.0 OSGi bundle com.ibm.mq.osgi.allclient_<version_number>.jar who use IBM MQ classes for Java to connect to a queue manager. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: The problem occurred when an application used the com.ibm.mq.osgi.allclient_<version_number>.jar OSGi bundle and attempted to establish a connection to a queue manager. At this point, an exception would be generated indicating that the internal com.ibm.msg.client.wmqcomponent could not be loaded, an example of this exception for JMS applications is shown below: detailMessage "JMSCC0091: The provider factory for connection type 'com.ibm.msg.client.wmq' could not be loaded." linkedException CSIException detailMessage "A Messaging Provider component was not found." The connection is unable to be successfully established. This was due to the fact that the OSGi bundle com.ibm.mq.osgi.allclient_<version_number>.jar only registered a single internal component to the MQ messaging provider component manager and therefore did not register all of the components required to run classes for Java and classes for JMS applications. Consequently, when there was an attempt to get an instance of the internal com.ibm.msg.client.wmq component for JMS applications to use, this failed, as the component had not been loaded. Additionally, if IBM MQ classes for Java were used to establish a connection to a queue manager, the following exception would be generated: java.lang.ClassNotFoundException: javax.transaction.xa.XAException not found by com.ibm.mq.osgi.allclient This was due to the fact that the OSGi bundle com.ibm.mq.osgi.allclient_<version_number>.jar did not import all packages required to run classes for Java applications.
Problem conclusion
The com.ibm.mq.osgi.allclient_<version_number>.jar OSGi bundle has now been updated so that it now registers all the internal components, and imports all packages, required to run classes for Java and classes for JMS applications with the MQ messaging provider component manager. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v8.0 8.0.0.9 v9.0 CD 9.0.5 v9.0 LTS 9.0.0.4 The latest available maintenance can be obtained from 'WebSphere MQ Recommended Fixes' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 If the maintenance level is not yet available information on its planned availability can be found in 'WebSphere MQ Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT22713
Reported component name
IBM MQ BASE MP
Reported component ID
5724H7251
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-10-09
Closed date
2018-01-29
Last modified date
2018-01-29
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
IBM MQ BASE MP
Fixed component ID
5724H7251
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.0.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
29 January 2018