Fixes are available
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
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
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
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.
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 V6.1.0 and V8.0 on z/OS * **************************************************************** * 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 PM38627 is currently targeted for inclusion in Service Level (Fix Pack) 6.1.0.41 of WebSphere Application Server V6.1. and Fix Pack 8.0.0.1 of WebSphere Application Server V8.0. Sysroute APAR PM46035 will be used to deliver this fix in 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
PM38627
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-05-06
Closed date
2011-06-23
Last modified date
2011-12-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
WEBSPHERE FOR Z
Fixed component ID
5655I3500
Applicable component levels
R610 PSY UK73054
UP11/11/03 P F111
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.
Document Information
Modified date:
27 October 2021