PM80934: JMS REGISTRATION ERROR MESSAGE WSVR0501E CAUSED BY NULLPOINTEREXCEPTION

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • During server startup, JMS Registration fails with a WSVR0501E
    message.  An FFDC is produced with the following stack:
    
    [11/11/12 4:59:32:561 EST]     FFDC
    Exception:java.lang.NullPointerException SourceId:null
    ProbeId:1011
    Reporter:com.ibm.ws.runtime.component.ContainerHelper@7b3c7b3c
    java.lang.NullPointerException
    at
    org.eclipse.core.runtime.internal.adaptor.CachedManifest.keys(Ca
    chedManifest.java:63)
    at
    org.eclipse.osgi.framework.internal.core.ManifestLocalization.ge
    tHeaders(ManifestLocalization.java:57)
    at
    org.eclipse.osgi.framework.internal.core.AbstractBundle.getHeade
    rs(AbstractBundle.java:994)
    at
    org.eclipse.osgi.framework.internal.core.AbstractBundle.getHeade
    rs(AbstractBundle.java:942)
    at
    com.ibm.ejs.jms.JMSRegistrationHelper.getOSGiInstall(JMSRegistra
    tionHelper.java:837)
    at
    com.ibm.ejs.jms.JMSRegistrationHelper.install(JMSRegistrationHel
    per.java:232)
    at
    com.ibm.ejs.jms.JMSRegistrationHelper.installProvider(JMSRegistr
    ationHelper.java:149)
    at
    com.ibm.ejs.jms.JMSRegistration.initialize(JMSRegistration.java:
    240)
    at
    com.ibm.ws.runtime.component.ContainerHelper.initWsComponent(Con
    tainerHelper.java:1191)
    ...
    
    The server starts but WebSphere MQ JMS cannot be used.
    

Local fix

  • Remove
    MQ_CLEAR_MQ_FROM_OSGI_CACHE_ON_SHUTDOWN as an immediate
    workaround.  There should be no negative performance impact (as
    mentioned above, any effect would be positive owing to better
    usage of
    the OSGI cache.)
    
    With this variable removed, there is one notable risk - if
    the MQ
    binaries are updated, it could cause them to become out of sync
    with
    the OSGi cache on the WAS server.  To resolve this you should
    execute
    the "osgiCfgInit.sh" script from the WAS_HOME/bin directory.  A
    default
    execution of the script will clear the caches for WAS_HOME and
    the
    default profile; if there are multiple profiles, the script
    should be
    run with the "-all" parameter to recreate all caches.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server WebSphere MQ JMS                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: JMS Registration fails with WSVR0501E   *
    *                      message during server startup.  As a    *
    *                      result WebSphere MQ JMS cannot be       *
    *                      used.                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The OSGi framework used by WebSphere Application Server
    servers share a storage area on disk between servers in the
    same node.  When the WebSphere MQ JMS bundle is installed into
    the framework, a race condition exists between the servers
    which could cause files to be written/re-written to the shared
    location by one server while another server is reading those
    files.
    This can cause problems similar to this NullPointerException.
    Other symptoms of this problem are possible.
    This problem is likely to be exacerbated when the
    MQ_CLEAR_MQ_FROM_OSGI_CACHE_ON_SHUTDOWN variable is set.
    

Problem conclusion

  • This APAR adds the following new WebSphere variable.
    
    Name:         MQ_USE_BUNDLE_REFERENCE_INSTALL
    Valid values: true / false (default)
    Valid scopes: Cell or Node (do not customize at Server scope)
    
    When the variable is set to 'true', the WebSphere MQ JMS
    bundle is installed using a reference install. A reference
    install avoids the race condition by avoiding the need for the
    bundle manifest data to be be persisted by the OSGi framework.
    
    If this variable is not set then the behaviour is unchanged.
    
    If MQ_CLEAR_MQ_FROM_OSGI_CACHE_ON_SHUTDOWN is set, it is
    recommended that this variable be set at the same scope.
    
    APAR PM80934 requires changes to documentation.
    
    NOTE: Periodically, we refresh the documentation on our
    website; so the changes might have been made before you
    read this text. To access the latest on-line documentation,
    go to the product library page at:
    
    http://www.ibm.com/software/webservers/appserv/library
    
    The following update to the WebSphere Application Server
    Version 7.0 Information Center will be made available in
    December 2013.
    
    The topic "Installing WebSphere MQ to interoperate with
    WebSphere Application Server" will be updated to include the
    following optional step:
    
    7. (Optional:) Set the WebSphere Application Server
    MQ_USE_BUNDLE_REFERENCE_INSTALL environment variable to 'true'.
    When this variable is set to 'true', the WebSphere MQ JMS
    bundle is installed using a reference installation.
    
    (For IBM i and Distributed Platforms) The OSGi framework
    shares a storage area on disk. Because all servers of the
    installation use this storage area, multiple servers in the
    installation might read and or write data to this storage area
    concurrently, causing resource contention. The likelihood of a
    contention scenario occurring increases if the
    MQ_CLEAR_MQ_FROM_OSGI_CACHE_ON_SHUTDOWN variable is set to
    'true'. Setting the MQ_USE_BUNDLE_REFERENCE_INSTALL variable to
    'true' causes the WebSphere MQ JMS bundle to be installed using
    a reference installation, thereby avoiding the need for the
    OSGi framework to persist the WebSphere MQ JMS bundle file to
    the shared storage area. Instead, each server creates a unique
    bundle file for its use.
    
    (For z/OS Platform) The OSGi framework shares a storage area
    on disk. Because all servers of the installation use this
    storage area, multiple servers in the installation might read
    and or write data to this storage area concurrently, causing
    resource contention. The likelihood of a contention scenario
    occurring increases if the
    MQ_CLEAR_MQ_FROM_OSGI_CACHE_ON_SHUTDOWN variable is set to
    'true'. Setting the MQ_USE_BUNDLE_REFERENCE_INSTALL variable to
    'true'causes the WebSphere MQ JMS bundle to be installed using
    a reference installation, thereby avoiding the need for the
    OSGi framework to persist the WebSphere MQ JMS bundle file to
    the shared storage area. Instead, each server and controller
    creates a unique bundle file for its use.
    
    APAR PM80934 is currently targeted for inclusion in WebSphere
    Application Server Fix Packs 7.0.0.31, 8.0.0.7, and 8.5.5.1
    of WebSphere Application Server.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

  • Run osgiCfgInit on the affected profile and then start each
    server on the node one at a time, waiting 30 seconds between
    starts.
    

Comments

APAR Information

  • APAR number

    PM80934

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-01-18

  • Closed date

    2013-05-08

  • Last modified date

    2014-02-05

  • 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 FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY UI13725

       UP14/01/11 P F401

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.



Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Application Server for z/OS
General

Software version:

7.0

Reference #:

PM80934

Modified date:

2014-02-05

Translate my page

Machine Translation

Content navigation