All Forums Connectivity
pallila 4 posts Joined 10/12
15 Aug 2013
Connection timeout problem Driver version 13.10

We are seeeing connection timeout problems via teradata java driver v13.10. We tried to set the connection keep alive from the connection pool manager, still no luck. we still the socket failure excrption. Any pointers what could be done to get around this issue? Any solution ASAP would really help.

ERROR org.hib

ernate.util.JDBCExceptionReporter [Teradata JDBC Driver] [TeraJDBC] [Error 804] [SQLState 08S01] Socket communication failure for

Packet receive Thu Aug 08 19:15:46 UTC 2013 socket orig=dzdtddsl local= remote=dzdtddslcop1/ keepalive=

unavailable nodelay=unavailable receive=unavailable send=unavailable linger=unavailable traffic=unavailable concurrent=3 contimeout=10000 conw

ait=1000 connecttime=4 connecttotaltime=22 connectattempts=1 connectfailures=0 failurecache={} cid=7c20170b sess=1043725

Incomplete LAN message header: read 0 bytes  at  at com.teradata.jdbc.j :818)  at com.teradata.jdbc.jdbc_4.statemachine.StatementReceive State.action(StatementRe  at com.teradata.jdbc.jdbc_4.statemachine.StatementControl ler.runBody(  at com.teradata.jdbc  at com.teradata.jdbc.jdbc_4.TDStatement.executeStatement( TDStateme  at com.teradata.jdbc.jdbc_4.TDStatement.prepareRequest(TD  at com.teradata.jdbc.jdbc_4.TDPreparedStatement.<i

nit>(  at com.teradata.jdbc.jdk6.JDK6_SQL_PreparedStatement.<ini t>(  at com.ter

adata.jdbc.jdk6.JDK6_SQL_Connection.constructPreparedS tatement(  at com.teradata.jdbc.jdbc_4.TDSession.prepareStat

ement(  at com.teradata.jdbc.jdbc_4.TDSession.prepareStatement(TD  at sun.reflect.GeneratedMethodAccesso

r896.invoke(Unknown Source)  at sun.reflect.DelegatingMethodAccessorImpl.invoke(Delega  at java.lang.reflect.Me

thod.invoke(  at msjava.dbpool.connectionwrapper.internal.JdbcProxyingU tils$SQLExceptionHandlingInvocationHandler.invoke(Jdbc P  at $Proxy27.prepareStatement(Unknown Source)  at msjava.dbpool.connectionwrapper.internal.DelegatingCon nection.prepare


tomnolan 594 posts Joined 01/08
15 Aug 2013

According to the stack trace you posted, you are using Teradata JDBC Driver
You should upgrade to a newer version of the Teradata JDBC Driver; for example, Teradata JDBC Driver, that includes the fix for JDBC DR 155367 "Intermittent socket communication failures when using setQueryTimeout with large result sets"
Assuming that you obtain that fix, if you continue to receive Error 804, please be aware that Error 804 can occur for different reasons. The exception error message is important for distinguishing the different error conditions.
Typically, Error 804 with the error message "Socket communication failure for Packet receive" means that a network communication failure occurred. This can be due to a variety of reasons, such as:
1. Network problem
2. Teradata Database restart
3. Teradata session was aborted by Teradata Manager, Teradata Viewpoint, or some other administrator process that aborts idle sessions

pallila 4 posts Joined 10/12
20 Aug 2013

Will upgrade the driver and see if the exception goes  away [apart from validating that the conns are not getting killed]
Thanks Tom!!

You must sign in to leave a comment.