Symptom
- Customers using Java applications connecting to IQ with the legacy jconn4.jar jConnect JDBC driver (com.sybase.jdbc4.jdbc.SybDriver) making use of the DEFAULT_QUERY_TIMEOUT and INTERNAL_QUERY_TIMEOUT connection properties to facilitate setting a query time out value to terminate query statements that are taking too long to run.
- When converting applications to using the SQLAnywhere JDBC driver (sap.jdbc4.sqlanywhere.IDriver) there is no connection property for setting a query statement timeout value.
- java errors seen for a timeout using the jConnect driver
java.sql.SQLException: JZ006: Caught IOException: java.net.SocketTimeoutException: Read timed out use getCause() to see the error chain
at com.sybase.jdbc4.jdbc.ErrorMessage.raiseErrorCheckDead(ErrorMessage.java:1134)
at com.sybase.jdbc4.tds.Tds.handleIOE(Tds.java:5106)
at com.sybase.jdbc4.tds.Tds.handleIOE(Tds.java:5051)
...
at testDriver.TestDriver.main(TestDriver.java:42)
Caused by: java.net.SocketTimeoutException: Read timed out
Read more...
Environment
- SAP IQ 16.0 on all platforms
- SAP IQ 16.1 on all platforms
Product
SAP IQ 16.0 ; SAP IQ 16.1
Keywords
sybase, 'jconn4.jar', sajdbc, jcon4, jconn4, 'jconn 4', 'time out', fail, abort, terminate, drop, ASA, IAnywhere, 'SQL Anywhere', sqlanywhere, jdbc , KBA , BC-SYB-IQ , Sybase IQ , How To
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview