PI32943: Spurious FFDC reporting javax.management.InstanceNotFoundExcepti on

8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• Attempting to access an mbean in the Liberty profile server
  may result in an FFDC reporting a
  javax.management.InstanceNotFoundException.  We have only
  observed this when the mbean has been made unavailable, so
  that the attempt to access it would fail and the client
  receive the javax.management.InstanceNotFoundException.  It
  is theoretically possible for this problem to occur even if
  the mbean is still registered.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Liberty Profile                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Spurious FFDC reporting                 *
  *                      javax.management.InstanceNotFoundExcept *
  *                      ion                                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Attempting to access an MBean in the Liberty profile server may
  result in an FFDC reporting a
  javax.management.InstanceNotFoundException.  We have only
  observed this when the MBean has been made unavailable, so that
  the attempt to access it would fail and the client receive the
  javax.management.InstanceNotFoundException.  It is theoretically
  possible for this problem to occur even if the MBean is still
  registered.
  

Problem conclusion

• The framework managing registering certain OSGI services as
  MBeans was altered to correctly deal with several situations,
  including the OSGI service providing the MBean implementation
  being temporarily unavailable (the cause of this situation).
  
  The fix for this APAR is currently targeted for inclusion in fix
  pack 8.5.5.5.  Please refer to the Recommended Updates page for
  delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

• Ignore the FFDC
  

Comments

APAR Information

• 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

  WAS LIBERTY COR

• Fixed component ID

  5725L2900

Applicable component levels

• R855 PSY

     UP