Fix (APAR): PK33254 Status: Fix Release: 6.0.2.19,6.0.2.17,6.0.2.15,6.0.2.13 Operating System: AIX,HP-UX,Linux,Linux pSeries,Linux Red Hat - pSeries,Solaris,Windows Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 733318 Date: 2007-04-03 Abstract: A file from the WebSphere Connect JDBC driver interferes with the DataDirect Connect JDBC driver, causing a VerifyError. Description/symptom of problem: PK33254 resolves the following problem: ERROR DESCRIPTION: The following exception is encountered after upgrading to WebSphere V6.0.2.13 with APAR PK24997: ServletWrappe E SRVE0068E : java.lang.VerifyError: class:com/ddtek/jdbc/sqlserver/tds/TDSConnection, method.... Wrong return type in method at com.ddtek.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source) =============================================================== APAR PK24997 is included in WebSphere 6.0.2.13 and above which includes the version of WebSphere embedded Connect JDBC Driver: [IBM][SQLServer JDBC Driver]Driver Version: 3.40.87 This version of the JDBC Driver causes the problem. LOCAL FIX: N/A PROBLEM SUMMARY USERS AFFECTED: WebSphere Application Server version 6.0.2 users of the DataDirect Connect JDBC driver. PROBLEM DESCRIPTION: A file from the WebSphere Connect JDBC driver interferes with the DataDirect Connect JDBC driver, causing a VerifyError. RECOMMENDATION: None When the DataDirect Connect JDBC driver is used, the following error occurs: Exception in thread "main" java.lang.VerifyError: (class: co m/ddtek/jdbc/sqlserver/tds/TDSConnection, method: createSecurity Context, signature: (java/lang/String;java/lang/String;java/lang /String;) com/ddtek/util/UtilSecurityContext;) Wrong return type in function at com.ddtek.jdbc.sqlserver.SQLServerImplConnection.open( Unknown Source) at com.ddtek.jdbc.base.BaseConnection.connect(Unknown Sou rce) at com.ddtek.jdbc.base.BaseConnection.setupImplConnection (Unknown Source) at com.ddtek.jdbc.base.BaseConnection.open(Unknown Source ) at com.ddtek.jdbcx.base.BaseDataSource.getBaseConnection( Unknown Source) at com.ddtek.jdbcx.base.BaseDataSource.getPooledConnectio n(Unknown Source) at SqlServerDatasourceTest.connect(SqlServerDatasourceTes t.java:70) at SqlServerDatasourceTest.main(SqlServerDatasourceTest.j ava:41 PROBLEM CONCLUSION: The WebSphere Connect JDBC driver has been fixed to use file and package names that do not collide with the DataDirect Connect JDBC driver. The fix for this APAR is currently targeted for inclusion in fixpack 6.0.2.19. 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: