IBM Support

PM46035: STARTING DEPLOYMENT MANAGER INTERMITTENTLY RECEIVES JAVAX.MANAGEMENT.MBEANEXCEPTION IN GETATTRIBUTE METHOD.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • During the Deployment Manager startup the CR intermittently
    received the javax.management.MBeanException, and FFDC recorded
    javax.management.InstanceNotFoundException.
    .
    Trace: 2011/04/24 02:13:42.599 01 t=7A7580 c=UNK key=S2
    (13007002)
      ThreadId: 00000024
      FunctionName: com.ibm.ws.management.AdminServiceImpl
      SourceId: com.ibm.ws.management.AdminServiceImpl
      Category: AUDIT
      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(AdminService
    Impl.java:763)
      at
    com.ibm.ws.management.AdminServiceImpl.getAttribute(AdminService
    Impl.java:708)
      at
    com.ibm.ws.management.status.DeploymentManagerStatusCache.refres
    hCache(DeploymentManagerStatusCache.java:762)
      at
    com.ibm.ws.management.status.DeploymentManagerStatusCache._sendR
    eport(DeploymentManagerStatusCache.java:341)
      ...
    Caused by: javax.management.MBeanException: Exception thrown in
    RequiredModelMBean while trying to invoke operation getName
    .
    .
    FFDC showed:
      Caused by: javax.management.InstanceNotFoundException:
    Non-existant servant00000E2000000001
        at
    com.ibm.ws390.management.ServantMBeanInvoker.getServantMBeanAttr
    ibute(ServantMBeanInvoker.java:1494)
        at
    com.ibm.ws390.management.ServantMBeanInvoker.getAnyServantMBeanA
    ttribute(ServantMBeanInvoker.java:1355)
        at
    com.ibm.ws390.management.ProxyMBeanSupport.mbeanGetterSimple(Pro
    xyMBeanSupport.java:957)
        at
    com.ibm.ws390.management.proxy.ServantMBeanInvokerProxy.mbeanInv
    okerSimple(ServantMBeanInvokerProxy.java:1077)
        at
    com.ibm.ws390.management.proxy.ServantMBeanInvokerProxy.invoke(S
    ervantMBeanInvokerProxy.java:939)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of IBM WebSphere Application       *
    *                 Server V7.0                                  *
    *                                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: During the Deployment Manager           *
    *                      startup, the Control Region may         *
    *                      receive a                               *
    *                      javax.management.MBeanException, and    *
    *                      FFDC recorded                           *
    *                      javax.management.InstanceNotFoundExcept *
    *                      ion.   These do not                     *
    *                      indicate operational issues             *
    *                      as subsequent mbean calls work          *
    *                      fine after servant.started is           *
    *                      received.                               *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The DeploymentManager status cache code tries to refresh its
    information about applications by calling
    the Application mbean in its servant.  If the
    websphere.ws390.servant.started notification
    has not been received yet at the control region, then this may
    cause exceptions in the control region:
    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(AdminService
    Impl.java:763)
    at
    com.ibm.ws.management.AdminServiceImpl.getAttribute(AdminService
    Impl.java:708)
    at
    com.ibm.ws.management.status.DeploymentManagerStatusCache.refres
    hCache(DeploymentManagerStatusCache.java:762)
    There may also be an FFDC log created which shows:
    Caused by: javax.management.InstanceNotFoundException:
    Non-existant servant00000E2000000001
    at
    com.ibm.ws390.management.ServantMBeanInvoker.getServantMBeanAttr
    ibute(ServantMBeanInvoker.java:1494)
    at
    com.ibm.ws390.management.ServantMBeanInvoker.getAnyServantMBeanA
    ttribute(ServantMBeanInvoker.java:1355)
    at
    com.ibm.ws390.management.ProxyMBeanSupport.mbeanGetterSimple(Pro
    xyMBeanSupport.java:957)
    at
    com.ibm.ws390.management.proxy.ServantMBeanInvokerProxy.mbeanInv
    okerSimple(ServantMBeanInvokerProxy.java:1077)
    at
    com.ibm.ws390.management.proxy.ServantMBeanInvokerProxy.invoke(S
    ervantMBeanInvokerProxy.java:939)
    
    
    In another case, the TraceService MBean proxy code was also
    noticed to have the same issue with InstanceNotFoundException.
    javax.management.InstanceNotFoundException: Non-existant
    servant0000039000000003
      at
    com.ibm.ws390.management.ServantMBeanInvoker.invokeServantMBean(
    ServantMBeanInvoker.java:1046)
      at
    com.ibm.ws390.management.ServantMBeanInvoker.invokeAnyServant(Se
    rvantMBeanInvoker.java:856)
      at
    com.ibm.ws390.management.ServantMBeanInvoker.invokeSpecificServa
    nt(ServantMBeanInvoker.java:467)
      at
    com.ibm.ws390.management.proxy.TraceServiceMBeanProxy$SetRuntime
    TraceSpecification.run(TraceServiceMBeanProxy.java:1246)
    

Problem conclusion

  • The code has been modified to wait for
    websphere.ws390.servant.started notification.
    
    APAR PM46035 is currently targeted for inclusion in Service
    Level (Fix Pack) 7.0.0.19 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

    PM46035

  • 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

    2011-08-18

  • Closed date

    2011-08-25

  • Last modified date

    2011-10-04

  • APAR is sysrouted FROM one or more of the following:

    PM38627

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • BBGUBINF BBOUBINF
    

Fix information

  • Fixed component name

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY UK71297

       UP11/09/10 P F109

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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
10 February 2022