Fix (APAR): PK45268 Status: Fix Release: 6.0.2.19 Operating System: AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux Red Hat - pSeries,Linux zSeries,OS/390,OS/400,Solaris,Windows Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 19021 Date: 2007-05-21 Abstract: DSRA9010E occurs on lookups of datasources when using the IBM Relational Resouce Adapter in IBM WebSphere Application Server Description/symptom of problem: PK45268 resolves the following problem: ERROR DESCRIPTION: In WebSphere Application Server V6.0.2.19, every time an application that is using a standard (not Version 4) data source (using the IBM Relational Resource Adapter) does a JNDI lookup to get a data source object, the following error message appears in the SystemOut.log: . DSRA9010E: 'setPurgePolicy' is not supported on the WebSphere interface javax.resource.spi.ManagedConnectionFactory implementation. . Despite the error message, the connection request will proceed normally and should be successful. The Purge Policy that is set in the connection pool properties (either "EntirePool" or "FailingConnectionOnly") will still be used. . The impact of the problem is minimal and the only impact is that a large number of DSRA9010E errors will appear in the SystemOut.log. The number of DSRA9010E messages is dependent on the number of times a JNDI lookup of the data source is done. The error will occur less often when applications lookup a data source once and cache it for getConnection requests. LOCAL FIX: none PROBLEM SUMMARY USERS AFFECTED: User of IBM WebSphere Application Server version 6.0.2 who have applicaitons that use the IBM Relational Resouce Adapter. PROBLEM DESCRIPTION: DSRA9010E occurs on lookups of datasources when using the IBM Relational Resouce Adapter in IBM WebSphere Application Server RECOMMENDATION: None In WebSphere Application Server V6.0.2, every time an application that is using the IBM Relational Resource Adapter does a lookup of a datasource. The following message will appear. DSRA9010E: 'setPurgePolicy' is not supported on the WebSphere interface javax.resource.spi.ManagedConnectionFactory implementation. - Despite the error message, the connection request will proceed normally and should be successful. The error does not prevent the Purge Policy that is set in the connection pool from being used. The Purge Policy that is configured on a connection pool will still be used. PROBLEM CONCLUSION: The impact of this should be minimal since most applications do a look up of a datasource once and then cache the datasource to use for get connection requests. But this APAR will change the code so the warning message is not displayed. The fix for this APAR is currently targeted for inclusion in fixpack 6.0.2.21. Please refer to the recommended updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 Directions to apply fix: NOTE: Choose the: 1) Release the fix applies to 2) The Editions that apply 3) Delete the Editions & Methods that do not apply and this Note Fix applies to Editions: Release 6.0 __ Application Server (Express or BASE) __ Network Deployment (ND) __ WebSphere Business Integration Server Foundation (WBISF) __ Edge Components __ Developer __ Extended Deployment (XD) Install Fix to: Method: __ Application Server Nodes __ Deployment Manager Nodes __ Both NOTE: The user must: * Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V6.0.2.2 or newer of the Update Installer. This can be checked by reviewing the level of the Update Installer in file /updateinstaller/version.txt. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 For detailed instructions to Extract the Update Installer see the following Technote: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400 1) Copy PKxxxxx.pak file directly to the maintenance directory 2) Shutdown WebSphere Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to. 3) Launch Update Installer 4) Enter the installation location of the WebSphere product you want to update. 5) Select the "Install maintenance package" operation. 6) Enter the file name of the maintenance package to install (PKxxxxx.pak file which was copied in the maintenance directory). 7) Install the maintenance package. 8) Restart WebSphere Directions to remove fix: NOTE: * The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED * DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED * YOU MAY REAPPLY ANY REMOVED FIX Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied. 1) Shutdown WebSphere Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against. 2) Start Update Installer 3) Enter the installation location of the WebSphere product you want to remove the fix. 4) Select "Uninstall maintenance package" operation. 5) Enter the file name of the maintenance package to uninstall (PKxxxxx.pak). 6) UnInstall maintenance package. 7) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere. 2) Follow the Fix instructions to apply the fix. 3) Restart WebSphere. Additional Information: