Fixes are available
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
Rational Quality Manager 6.0
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.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
A customer driver is throwing an SQLException with an error code indicating "Not supported" instead of throwing a SQLFeatureNotSupportedException. According to various specs, valid ways of indicating that a SQLException is a not supported exception are: - SQLState = 0A000 - err code = 0x0A000 - SQLState = HYC00 [ERROR ] J2CA0081E: Method cleanup failed while trying to execute method cleanup on ManagedConnection WSRdbManagedConnectionImpl@2029e4ff from resource jdbc/crmDatabase. Caught exception: com.ibm.ws.rsadapter.exceptions.DataStoreAdapterException: DSRA0080E: An exception was received by the Data Store Adapter. See original exception message: The Connection.setTypeMap(Map) method is not implemented.. at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanupS tates(WSRdbManagedConnectionImpl.java:3658) at [internal classes] at org.springframework.jdbc.datasource.DataSourceUtils.doReleas eConnection(DataSourceUtils.java:313) at org.springframework.jdbc.datasource.DataSourceUtils.releaseC onnection(DataSourceUtils.java:274) at org.springframework.jdbc.datasource.DataSourceTransactionMan ager.doCleanupAfterCompletion(DataSourceTransactionManager.j ava:316) at org.springframework.transaction.support.AbstractPlatformTran sactionManager.cleanupAfterCompletion(AbstractPlatformTransa ctionManager.java:966) at org.springframework.transaction.support.AbstractPlatformTran sactionManager.processCommit(AbstractPlatformTransactionMana ger.java:759) at org.springframework.transaction.support.AbstractPlatformTran sactionManager.commit(AbstractPlatformTransactionManager.jav a:678) at org.springframework.transaction.interceptor.TransactionAspec tSupport.commitTransactionAfterReturning(TransactionAspectSu pport.java:321) at org.springframework.transaction.interceptor.TransactionInter ceptor.invoke(TransactionInterceptor.java:116) at org.springframework.aop.framework.ReflectiveMethodInvocation .proceed(ReflectiveMethodInvocation.java:171) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke( JdkDynamicAopProxy.java:204) at com.sun.proxy.$Proxy30.getUnspecifiedItems(Unknown Source) at com.dbo2.pipeline.model.safety.SafetyService.getUnspecifiedI tems(SafetyService.java:289) at com.dbo2.pipeline.controller.dashboard.YUIDashboardAction.pr ocessNotifications(YUIDashboardAction.java:192) at com.dbo2.pipeline.controller.dashboard.YUIDashboardAction.pr ocess(YUIDashboardAction.java:54) at com.dbo2.pipeline.controller.AbstractAction.execute(Abstract Action.java:172) at org.apache.struts.action.RequestProcessor.processActionPerfo rm(RequestProcessor.java:484) at org.apache.struts.action.RequestProcessor.process(RequestPro cessor.java:274) at org.apache.struts.action.ActionServlet.process(ActionServlet .java:1482) at com.dbo2.pipeline.web.PipelineActionServlet.process(Pipeline ActionServlet.java:110) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.j ava:507) at javax.servlet.http.HttpServlet.service(HttpServlet.java:575) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(Servl etWrapper.java:1285) at [internal classes] at org.apache.struts.action.RequestProcessor.doForward(RequestP rocessor.java:1069) at org.apache.struts.action.RequestProcessor.processForwardConf ig(RequestProcessor.java:455) at org.apache.struts.action.RequestProcessor.process(RequestPro cessor.java:279) at org.apache.struts.action.ActionServlet.process(ActionServlet .java:1482) at com.dbo2.pipeline.web.PipelineActionServlet.process(Pipeline ActionServlet.java:110) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.j ava:507) at javax.servlet.http.HttpServlet.service(HttpServlet.java:575) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(Servl etWrapper.java:1285) at [internal classes] Caused by: java.sql.SQLException: The Connection.setTypeMap(Map) method is not implemented. DSRA0010E: SQL State = HYC00, Error Code = 0 at net.sourceforge.jtds.jdbc.JtdsConnection.notImplemented(Jtds Connection.java:1769) at net.sourceforge.jtds.jdbc.JtdsConnection.setTypeMap(JtdsConn ection.java:2394) at net.sourceforge.jtds.jdbcx.proxy.ConnectionProxy.setTypeMap( ConnectionProxy.java:666) at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.setTypeM ap(WSRdbManagedConnectionImpl.java:4838)
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty Profile - Database Access * **************************************************************** * PROBLEM DESCRIPTION: Cleanup fails with an SQLException for * * unsupported operations * **************************************************************** * RECOMMENDATION: * **************************************************************** JDBC 3.0 and earlier drivers that do not support optional JDBC operations throw an SQLException with an error code indicating not supported, rather than using the SQLFeatureNotSupportedException introduced with the JDBC 4.0 spec.
Problem conclusion
Toleration has been added in the WebSphere connection cleanup code to allow for JDBC 3.0 and earlier drivers to throw a SQLException with an error code indicating operation not supported. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.6. 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
PI38333
Reported component name
WAS LIBERTY COR
Reported component ID
5725L2900
Reported release
855
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-04-03
Closed date
2015-04-20
Last modified date
2015-04-20
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
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSD28V","label":"WebSphere Application Server Liberty Core"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
28 April 2022