Fixes are available
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
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: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
After creating the JDBC provider and DataSource, connection to the database is working correctly, however MBean is created successfully, but runtime generated exception in FFDC as instance already exists. We can confirm that there is only one MBean is created in scope level of resources.xml file. Here is what incident reported in FFDC which is incorrect. FFDC:- ------ ------Start of DE processing------ = [7/25/07 14:30:36:386 CDT] , key = javax.management.InstanceAlreadyExistsException com.ibm.ws.management.MBeanFactoryImpl.activateMBean 190 Exception = javax.management.InstanceAlreadyExistsException Source = com.ibm.ws.management.MBeanFactoryImpl.activateMBean probeid = 190 Stack Dump = javax.management.InstanceAlreadyExistsException: WebSphere:name=Oracle JDBC Driver,process=server1,platform=dynamicproxy,node=acotxc9Node01, j2eeType =JDBCResource,J2EEServer=server1,Server=server1,version=6.1.0.9, type=JDB CProvider,mbeanIdentifier=cells/acotxc9Cell01/clusters/Provider/ resource s.xml#JDBCProvider_1183044406535,cell=acotxc9Cell01,spec=1.0 at com.sun.jmx.mbeanserver.RepositorySupport.addMBean(RepositorySup port.jav a:470) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_a ddObject (DefaultMBeanServerInterceptor.java:1428) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerOb ject(Def aultMBeanServerInterceptor.java:954) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMB ean(Defa ultMBeanServerInterceptor.java:355) at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanSer ver.java :515) at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactor yImpl.ja va:494) at com.ibm.ws.runtime.component.collaborator.J2EEResourceMBean.acti vate(J2E EResourceMBean.java:66) at com.ibm.ws.runtime.component.collaborator.J2EEResourceMBean.<ini t>(J2EER esourceMBean.java:47) at com.ibm.ws.runtime.component.collaborator.JDBCResourceMBean.<ini t>(JDBCR esourceMBean.java:36) at com.ibm.ws.runtime.component.binder.WAS40DataSourceBinder.activa teProvid erMBean(WAS40DataSourceBinder.java:157) at com.ibm.ws.runtime.component.ResourceMgrImpl.installResourceProv ider(Res ourceMgrImpl.java:1159) at com.ibm.ws.runtime.component.ResourceMgrImpl.installResource(Res ourceMgr Impl.java:1004) at com.ibm.ws.runtime.component.ResourceMgrImpl.installResources(Re sourceMg rImpl.java:957) at com.ibm.ws.runtime.component.ResourceMgrImpl.loadResources(Resou rceMgrIm pl.java:756) at com.ibm.ws.runtime.component.ResourceMgrImpl.start(ResourceMgrIm pl.java: 631) SystemOut.log: -------------- [7/25/07 14:30:36:339 CDT] 0000000a ResourceMgrIm I WSVR0049I: Binding txcompt as jdbc/TXCOMPDataSource [7/25/07 14:30:36:439 CDT] 0000000a ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl initialize FFDC0009I: FFDC opened incident stream file /opt/app/WebSphere6/AppServer/profiles/AppSrv01/logs/ffdc/server 1_c000c0 _07.07.25_14.30.36_0.txt Trace: ------ [7/25/07 14:30:36:292 CDT] 0000000a MBeanFactoryI < createMBeanName Exit WebSphere:name=Oracle JDBC Driver,process=server1,platform=dynamicproxy,node=acotxc9Node01, j2eeType =JDBCResource,J2EEServer=server1,Server=server1,version=6.1.0.9, type=JDB CProvider,mbeanIdentifier=cells/acotxc9Cell01/clusters/Provider/ resource s.xml#JDBCProvider_1183044406535,cell=acotxc9Cell01,spec=1.0 [7/25/07 14:30:36:385 CDT] 0000000a MBeanFactoryI < createMBeanName Exit WebSphere:name=Oracle JDBC Driver,process=server1,platform=dynamicproxy,node=acotxc9Node01, j2eeType =JDBCResource,J2EEServer=server1,Server=server1,version=6.1.0.9, type=JDB CProvider,mbeanIdentifier=cells/acotxc9Cell01/clusters/Provider/ resource s.xml#JDBCProvider_1183044406535,cell=acotxc9Cell01,spec=1.0 [7/25/07 14:30:36:439 CDT] 0000000a ServiceLogger I com.ibm.ws.ffdc.IncidentStreamImpl initialize FFDC0009I: FFDC opened incident stream file /opt/app/WebSphere6/AppServer/profiles/AppSrv01/logs/ffdc/server 1_c000c0 _07.07.25_14.30.36_0.txt
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM Websphere Application Server users of * * versions 6.0.2 and 6.1. * **************************************************************** * PROBLEM DESCRIPTION: Instance Already Exists Exception in * * FFDC logs directory for MBean. * **************************************************************** * RECOMMENDATION: * **************************************************************** After creating the JDBC provider and DataSource, connection to the database is working correctly. However an MBean is created successfully, but a runtime generated exception in FFDC is "instance already exists." We can confirm that there is only one MBean is created in scope level of resources.xml file. Here is Exception that is reported in FFDC which is incorrect. ------Start of DE processing------ = [7/25/07 14:30:36:386 CDT] , key = javax.management.InstanceAlreadyExistsException com.ibm.ws.management.MBeanFactoryImpl.activateMBean 190 Exception = javax.management.InstanceAlreadyExistsException Source = com.ibm.ws.management.MBeanFactoryImpl.activateMBean probeid = 190 Stack Dump = javax.management.InstanceAlreadyExistsException: WebSphere:name=Oracle JDBC Driver,process=server1,platform=dynamicproxy,node=acotxc9Node01, j2eeType =JDBCResource,J2EEServer=server1,Server=server1,version=6.1.0.9, type=JDB CProvider,mbeanIdentifier=cells/acotxc9Cell01/clusters/Provider/ resource s.xml#JDBCProvider_1183044406535,cell=acotxc9Cell01,spec=1.0 at com.sun.jmx.mbeanserver.RepositorySupport.addMBean(RepositorySup port.jav a:470) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_a ddObject (DefaultMBeanServerInterceptor.java:1428) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerOb ject(Def aultMBeanServerInterceptor.java:954) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMB ean(Defa ultMBeanServerInterceptor.java:355) at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanSer ver.java :515) at com.ibm.ws.management.MBeanFactoryImpl.activateMBean(MBeanFactor yImpl.ja va:494) at com.ibm.ws.runtime.component.collaborator.J2EEResourceMBean.acti vate(J2E EResourceMBean.java:66) .......... ..........
Problem conclusion
Modified the code to change the FFDC message into a debug message in both the runtime and admin components and only print the InstanceAlreadyExistException when the debug trace is enabled. The fix for this APAR is currently targeted for inclusion in fixpacks 6.0.2.25 and 6.1.0.13. Please refer to the recommended updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PK50151
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
60W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-08-01
Closed date
2007-09-17
Last modified date
2009-04-13
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
ADMINJMX
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
28 December 2021