IBM Support

IT23625: OSGi bundle com.ibm.mq.osgi.allclient_<version number>.jar does not export all of the required packages.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The WebSphere MQ V7.5 classes for JMS OSGi bundles:
    
    - com.ibm.msg.client.osgi.jms_7.5.0.x.jar
    - com.ibm.msg.client.osgi.jms.prereq_7.5.0.x.jar
    - com.ibm.msg.client.osgi.commonservices.j2se_7.5.0.x.jar
    - com.ibm.msg.client.osgi.nls_7.5.0.x.jar
    - com.ibm.msg.client.osgi.wmq_7.5.0.x.jar
    - com.ibm.msg.client.osgi.wmq.prereq_7.5.0.x.jar
    - com.ibm.msg.client.osgi.wmq.nls_7.5.0.x.jar
    - com.ibm.mq.osgi.directip_7.5.0.x.jar
    
    have been loaded into an OSGi framework. An application which is
    also loaded into the same OSGi framework is able to use the
    WebSphere MQ classes for JMS OSGi bundles to send messages to,
    and receive messages from, destinations hosted on an IBM MQ
    queue manager.
    
    The WebSphere MQ V7.5 OSGi bundles are then removed from the
    OSGi framework and replaced with the IBM MQ V9.0.0.2 allclient
    OSGi bundles:
    
    - com.ibm.mq.osgi.allclient_9.0.0.2.jar
    - com.ibm.mq.osgi.allclientprereqs_9.0.0.2.jar
    
    After doing so, the application is unable to run as the OSGi
    framework is unable to resolve the following packages:
    
    - com.ibm.msg.client.commonservices
    - com.ibm.msg.client.commonservices.Log
    - com.ibm.msg.client.commonservices.collections
    - com.ibm.msg.client.commonservices.workqueue
    - com.ibm.msg.client.jms.internal.resources
    - com.ibm.msg.client.provider
    - com.ibm.msg.client.services
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of:
    
    - The IBM MQ V9.0 OSGi bundle
    com.ibm.mq.osgi.allclient_<version_number>.jar
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    The WebSphere MQ V7.5 classes for JMS OSGi bundles:
    
    - com.ibm.msg.client.osgi.jms_7.5.0.x.jar
    - com.ibm.msg.client.osgi.jms.prereq_7.5.0.x.jar
    - com.ibm.msg.client.osgi.commonservices.j2se_7.5.0.x.jar
    - com.ibm.msg.client.osgi.nls_7.5.0.x.jar
    - com.ibm.msg.client.osgi.wmq_7.5.0.x.jar
    - com.ibm.msg.client.osgi.wmq.prereq_7.5.0.x.jar
    - com.ibm.msg.client.osgi.wmq.nls_7.5.0.x.jar
    - com.ibm.mq.osgi.directip_7.5.0.x.jar
    
    export a number of packages, including:
    
    - com.ibm.msg.client.commonservices
    - com.ibm.msg.client.commonservices.Log
    - com.ibm.msg.client.commonservices.collections
    - com.ibm.msg.client.commonservices.workqueue
    - com.ibm.msg.client.jms.internal.resources
    - com.ibm.msg.client.provider
    - com.ibm.msg.client.services
    
    However, these packages were not exported by the IBM MQ V9 OSGi
    allclient bundle:
    
    - com.ibm.mq.osgi.allclient_<version number>.jar
    
    This meant that if an application that was previously using the
    WebSphere MQ V7.5 classes for JMS OSGi bundles was run in an
    OSGi framework that had the IBM MQ V9 allclient bundles loaded,
    the application would be unable to start as the OSGi framework
    was unable to resolve the packages:
    
    - com.ibm.msg.client.commonservices
    - com.ibm.msg.client.commonservices.Log
    - com.ibm.msg.client.commonservices.collections
    - com.ibm.msg.client.commonservices.workqueue
    - com.ibm.msg.client.jms.internal.resources
    - com.ibm.msg.client.provider
    - com.ibm.msg.client.services
    

Problem conclusion

  • The IBM MQ V9 allclient OSGi bundle:
    
    - com.ibm.mq.osgi.allclient_<version number>.jar
    
    has been updated so that it now exports the packages:
    
    - com.ibm.msg.client.commonservices
    - com.ibm.msg.client.commonservices.Log
    - com.ibm.msg.client.commonservices.collections
    - com.ibm.msg.client.commonservices.workqueue
    - com.ibm.msg.client.jms.internal.resources
    - com.ibm.msg.client.provider
    - com.ibm.msg.client.services
    
    This allows applications that were previously using the
    WebSphere MQ V7.5 classes for JMS OSGi bundles to continue
    working with the IBM MQ V9.0 allclient OSGi bundle.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    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

    IT23625

  • Reported component name

    IBM MQ BASE M/P

  • Reported component ID

    5724H7261

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-01-11

  • Closed date

    2018-01-30

  • Last modified date

    2018-01-30

  • 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 M/P

  • Fixed component ID

    5724H7261

Applicable component levels

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
30 January 2018