IBM Support

IC74997: NULLPOINTEREXCEPTION IS RECEIVED WHEN USING THE WEBSPHERE MQ CLIENT BUNDLES WITH LOTUS EXPEDITOR V6.2.1

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Lotus Expeditor V6.2.1 has an option to install the OSGi bundles
    of WebSphere MQ classes for JMS.  If the WebSphere MQ bundle is
    installed, then a NullPointerException is displayed.
    
    The error is only seen if the WebSphere MQ Java client is being
    used to connect to WebSphere MQ via the bundle.
    
    The error that is reported on the OSGi console for the customer
    is:
    Caused by: java.lang.ClassCastException:
    com.sun.jndi.ldap.LdapCtxFactory incompatible with
    javax.naming.spi.InitialContextFactory
    ... 25 more
    
    While this issue was discovered the user had JNDI and
    LDAP features used in bundles that do not utilize WebSphere MQ.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of the WebSphere MQ V7 Java Message
    Service (JMS) OSGi bundles on OSGi platforms like Lotus
    Expeditor, where the WebSphere MQ OSGi bundles are used in
    addition to other bundles that utilize the JNDI and LDAP
    features.
    
    Platforms affected:
    All Distributed (iSeries, all Unix and Windows) +Java
    ****************************************************************
    PROBLEM SUMMARY:
    The problem occurred due to the export of the JNDI and LDAP
    packages in the Manifest file for
    com.ibm.msg.client.osgi.wmq.prereq_version.jar conflicting with
    the same packages which were made available by the OSGi
    platform.
    

Problem conclusion

  • The fix ensures that the JNDI and LDAP packages exported
    by the bundle com.ibm.msg.client.osgi.wmq.prereq_version.jar are
    removed. These packages are supplied by the Java Runtime
    Environment (JRE) and are made available for use by other
    bundles in OSGi environment. As these packages are provided by
    the JRE environment they are not associated with a version, so
    the version scoping of the imports javax.naming and other system
    bundles in com.ibm.msg.client.osgi.jms and
    com.ibm.msg.client.osgi.wmq OSGi bundles have been removed as
    part of this APAR.
    
    These changes ensure that there is no conflict with the
    equivalent packages provided by the OSGi environment.
    
    The version scoping was introduced as part of the APAR IC72767.
    That was found not to be a complete fix to the problem reported,
    and so this follow on APAR has been raised.
    
    The following error may be seen in some OSGi environments as a
    result of the changes made in this APAR:
    
    Direct constraints which are unresolved:
      Missing imported package com.sun.jndi.ldap_0.0.0.
      Missing imported package com.sun.jndi.toolkit.corba_0.0.0.
      Missing imported package com.sun.jndi.toolkit.ctx_0.0.0.
      Missing imported package com.sun.jndi.toolkit.dir_0.0.0.
      Missing imported package com.sun.jndi.toolkit.url_0.0.0.
      Missing imported package com.sun.jndi.url.ldap_0.0.0.
    
    The com.sun.jndi package listed above are a part of the Java
    Runtime. The WebSphere MQ OSGi bundle
    com.ibm.msg.client.osgi.wmq optionally imports these bundles
    for certain administrative functionality, ie JMSAdmin and
    Install Verification Test tool.
    
    In the case where the JMSAdmin or Install Verification Test
    functionality needs to be used inside the OSGi environment, a
    system fragment may need to be created by the user which adds in
    exports for these packages if the OSGi environment does not
    provide access to these packages (that is, it does not use boot
    delegation to add them to the list of packages available as part
    of the JRE).
    
    A sample Manifest that can be used to create this system
    fragment bundle is provided below:
    
    Manifest-Version: 1.0
    Bundle-ManifestVersion: 2
    Bundle-Name: WMQ System Fragment
    Bundle-SymbolicName: wmq.system.fragment
    Bundle-Version: 1.0.0
    Fragment-Host: system.bundle;extension:=framework
    Export-Package: com.sun.jndi.ldap,
     com.sun.jndi.toolkit.corba,
     com.sun.jndi.toolkit.ctx,
     com.sun.jndi.toolkit.dir,
     com.sun.jndi.toolkit.url,
     com.sun.jndi.url.ldap
    
    If "com.sun.*" is added to the boot delegation, this
    error won't occur.
    
    | MDVPARTL 7.0.1-WS-MQ-AixPPC64-FP0005       |
    | MDVPARTL 7.0.1-WS-MQ-HpuxIA64-FP0005       |
    | MDVPARTL 7.0.1-WS-MQ-HpuxPaRISC64-FP0005   |
    | MDVPARTL 7.0.1-WS-MQ-LinuxIA32-FP0005      |
    | MDVPARTL 7.0.1-WS-MQ-LinuxPPC64-FP0005     |
    | MDVPARTL 7.0.1-WS-MQ-LinuxS390X-FP0005     |
    | MDVPARTL 7.0.1-WS-MQ-LinuxX64-FP0005       |
    | MDVPARTL 7.0.1-WS-MQ-SolarisSparc64-FP0005 |
    | MDVPARTL 7.0.1-WS-MQ-SolarisX64-FP0005     |
    | MDVPARTL 7.0.1-WS-MQ-Windows-FP0005        |
    
    
    | MDVPARTL 7.0.1-WS-MQ-AixPPC64-FP0006       |
    | MDVPARTL 7.0.1-WS-MQ-HpuxIA64-FP0006       |
    | MDVPARTL 7.0.1-WS-MQ-HpuxPaRISC64-FP0006   |
    | MDVPARTL 7.0.1-WS-MQ-LinuxIA32-FP0006      |
    | MDVPARTL 7.0.1-WS-MQ-LinuxPPC64-FP0006     |
    | MDVPARTL 7.0.1-WS-MQ-LinuxS390X-FP0006     |
    | MDVPARTL 7.0.1-WS-MQ-LinuxX64-FP0006       |
    | MDVPARTL 7.0.1-WS-MQ-SolarisSparc64-FP0006 |
    | MDVPARTL 7.0.1-WS-MQ-SolarisX64-FP0006     |
    | MDVPARTL 7.0.1-WS-MQ-Windows-FP0006        |
    
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v7.0
    Platform           Fix Pack 7.0.1.7
    --------           --------------------
    Windows            U200333
    AIX                U843721
    HP-UX (PA-RISC)    U844089
    HP-UX (Itanium)    U844094
    Solaris (SPARC)    U844090
    Solaris (x86-64)   U844096
    iSeries            tbc_p700_0_1_7
    Linux (x86)        U844091
    Linux (x86-64)     U844095
    Linux (zSeries)    U844092
    Linux (Power)      U844093
    
    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

    IC74997

  • Reported component name

    WMQ WINDOWS V7

  • Reported component ID

    5724H7220

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-03-14

  • Closed date

    2011-07-07

  • Last modified date

    2011-08-02

  • 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

    WMQ WINDOWS V7

  • Fixed component ID

    5724H7220

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCPQ63","label":"APAR \/ Maintenance"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 August 2011