IBM Support

PM15416: JAVAX.MANAGEMENT.MBEANEXCEPTION: EXCEPTION THROWN IN REQUIREDMODELMBEAN WHILE TRYING TO INVOKE OPERATION GETNAME

Fixes are available

7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • javax.management.InstanceNotFoundException seen in control
    region JVM log when starting a server on a z/OS system
    heavily loaded with many Java Management Extension (JMX)
    Management Beans (MBeans)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All IBM WebSphere Application Server        *
    *                  version 7.0 users on z/OS.                  *
    *                                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: A javax.management.                     *
    *                      InstanceNotFoundException may be seen   *
    *                      in the z/OS control region when         *
    *                      starting a server with many Java        *
    *                      Management Extension (JMX) Management   *
    *                      Beans (MBeans)                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Java Management Extension (JMX) Management Beans (MBeans) may be
    queued in the z/OS servant region awaiting ORB initialization
    before finishing registration in the z/OS control region (so
    that proxies can be created in the control region to the
    servant regions.)  If there are many MBeans queued, it may
    take some time to complete MBean registration.  Meanwhile,
    status cache refresh activity is triggered by a received
    notification of websphere.ws390.servant.started for a servant
    region. Because the MBean is not yet registered to the JVM by
    the CR, it is seen as not routable (no proxy exists to a
    servant region) and invocation is attempted locally.  This
    results in an exception with a stack trace like:
    ExtendedMessage: BBOO0222I: ADMN0007I:
    The getAttribute method results in exception
    com.ibm.websphere.management.exception.AdminException:
    javax.management.MBeanException: Exception thrown in
    RequiredModelMBean while trying to invoke operation getName
    at com.ibm.ws.management.AdminServiceImpl.getAttribute
    at com.ibm.ws.management.status.AbstractStatusCache
      .getAttribute
    at com.ibm.ws.management.status.AppServerStatusCache
      .refreshCache
    at com.ibm.ws.management.status.AppServerStatusCache
      ._sendReport
    at com.ibm.ws.management.status.AbstractStatusCache
      $StatusCacheRefreshThread.runPrivate
    at com.ibm.ws.management.status.AbstractStatusCache
      $StatusCacheRefreshThread.run
    Caused by: javax.management.MBeanException: Exception thrown
    in RequiredModelMBean while trying to invoke operation getName
    

Problem conclusion

  • The code is modified such that no exception is thrown when the
    getName operation is attempted by the StatusCache MBean when
    it is queued awaiting ORB initialization.
    
    APAR PM15416 is currently targeted for inclusion in Service
    Level (Fix Pack) 7.0.0.13 of WebSphere Application Server V7.0.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM15416

  • 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

    2010-05-27

  • Closed date

    2010-06-07

  • Last modified date

    2010-11-03

  • 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 UK61114

       UP10/10/21 P F010

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.

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021