All Forums Connectivity
Greyghost 51 posts Joined 07/09
15 Jun 2012
Socket Error 804

Does anyone know what would cause, or how to correct a Socket Error?  Below are the details of the error message:

"CAMSPROD","Error Executing Database Query.[Teradata JDBC Driver] [TeraJDBC 13.10.00.18] [Error 804] [SQLState 08S01] Socket communication failure for Packet receive Thu Jun 14 02:50:21 CDT 2012 socket orig=10.139.0.28 local=0.0.0.0/0.0.0.0:4379 remote=/10.139.0.28:1025 keepalive=unavailable nodelay=unavailable receive=unavailable send=unavailable linger=unavailable traffic=unavailable concurrent=3 contimeout=10000 conwait=1000 connecttime=0 connecttotaltime=16 connectattempts=1 connectfailures=0 failurecache={} cid=1031697 sess=231027 java.io.IOException: Incomplete LAN message header: read 0 bytes   at com.teradata.jdbc.jdbc_4.io.TDNetworkIOIF.read(TDNetwo rkIOIF.java:663)   at com.teradata.jdbc.jdbc_4.io.TDPacketStream.readStream( TDPacketStream.java:818)   at com.teradata.jdbc.jdbc_4.statemachine.StatementReceive State.action(StatementReceiveState.java:129)   at com.teradata.jdbc.jdbc_4.statemachine.StatementControl ler.runBody(StatementController.java:120)   at com.teradata.jdbc.jdbc_4.statemachine.StatementControl ler.r...

 

 

Thanks!

Paul

TDDeveloper 23 posts Joined 09/09
18 Jun 2012

Is this error repeatble or occurring at random? if occurring at random intervals try to increase the "concurrent" limit from 3 to 10. if you hit this error every single time, try uninstall reinstall the JDBC driver and check if the installation is ok then retry. If you again have the same problem open a ticket with GSC. - Thanks, Sankar

tomnolan 594 posts Joined 01/08
18 Jun 2012

Unfortunately, the previous poster's advice is not useful.

The "concurrent" setting is not related to this issue. (The "concurrent" setting is only relevant at connect time, is not documented, and is not intended to be changed for normal usage.)

Also, it is unlikely that uninstalling/reinstalling the Teradata JDBC Driver will affect this issue.

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

However, there is a known problem (JDBC DR 155367) with the Teradata JDBC Driver if your application is using setQueryTimeout and receiving a large result set from the Teradata Database (ResultSet containing more than 1MB of data). This problem is planned to be fixed in an upcoming release.

 

TDDeveloper 23 posts Joined 09/09
18 Jun 2012

(1) The socket connection is originating and ending at the same IP I don't think that could be a net work issue!!

(2) 'database restart' error most likely reported as an error of 'database restart' not 'socket error'.

(3) Any 'abort session' by user likely be reported as 'session aborted by peer' error..

 

Thx

 

Greyghost 51 posts Joined 07/09
18 Jun 2012

Thanks for the replies.  This is a process being run by a 3rd Party company supporting a Teradata process.  This error has occurred every night that they have tried to run the process.  My impression is that they are moving a large amount of data while doing this.

 

Thanks!

Paul

tomnolan 594 posts Joined 01/08
18 Jun 2012

Once again, please discount what "TDDeveloper" said.

The "orig" in the error message refers to the "original" Teradata Database hostname specified by the application; it does not mean "originating".

TDDeveloper -- please refrain from posting incorrect information, or you will be banned from the forums.

 

Greyghost 51 posts Joined 07/09
19 Jun 2012

Thanks Tom,

 

I will pass this info onto to our 3rd Party support team to see if this helps them with this issue.

 

Paul

asikri 1 post Joined 07/12
18 Jul 2012

Hey Paul,did you get a solution for this yet.I am also experiencing the same issue.any help will be really appreciated.Thanks.

yeyuancn 1 post Joined 04/11
04 Sep 2012

We saw this error on a customer's site when running a query like "select A.DatabaseName,A.TableName,A.TableKind  FROM DBC.TablesV A  WHERE TableKind = 'T' OR TableKind = 'O'". We suspect it is the size of data returned caused the error, will modify the query to limit the resultset.

tomnolan 594 posts Joined 01/08
14 Sep 2012

Teradata JDBC Driver 14.00.00.21 has been released and is now available for download here on Developer Exchange.
Teradata JDBC Driver 14.00.00.21 contains the fix for JDBC DR 155367.

charlesbernard 10 posts Joined 12/12
07 Jan 2013

 
Hi there, I'm using the latest release of the Teradata JDBC Driver (14.00.00.21) although I still get the same error:

[Error Code: 804, SQL State: 08S01]
[Teradata JDBC Driver] [TeraJDBC 14.00.00.21] [Error 804] [SQLState 08S01]
Socket communication failure for Packet receive Fri Jan 04 11:39:28 CET 2013 socket orig=xxxxxxx.xxx.xxx.xx local=0.0.0.0/0.0.0.0:62422 remote=xxxxxxx.xxx.xxx.xx/xxx.xx.xx.xx:1025 keepalive=unavailable nodelay=unavailable receive=unavailable send=unavailable linger=unavailable traffic=unavailable concurrent=3 contimeout=10000 conwait=1000 connecttime=0 connecttotaltime=0 connectattempts=1 connectfailures=0 failurecache={xxxxxxx.xxx.xxx.xx/xxx.xx.xx.xx:1025=Fri Jan 04 11:10:08 CET 2013} cid=731e0714 sess=4757 java.io.IOException: Incomplete LAN message header: read 0 bytes
at com.teradata.jdbc.jdbc_4.io.TDNetworkIOIF.read(TDNetworkIOIF.java:674)
at com.teradata.jdbc.jdbc_4.io.TDPacketStream.readStream(TDPacketStream.java:818)
at com.teradata.jdbc.jdbc_4.statemachine.StatementReceiveState.action(StatementReceiveState.java:143)
at com.teradata.jdbc.jdbc_4.statemachine.StatementController.runBody(StatementController.java:121)
at com.teradata.jdbc.jdbc_4.statemachine.StatementController.run(StatementController.java:112)
at com.teradata.jdbc.jdbc_4.TDStatement.executeStatement(TDStatement.java:375)
at com.teradata.jdbc.jdbc_4.TDStatement.executeStatement(TDStatement.java:317)
at com.teradata.jdbc.jdbc_4.TDStatement.doNonPrepExecute(TDStatement.java:280)
at com.teradata.jdbc.jdbc_4.TDStatement.execute(TDStatement.java:1087)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.onseven.dbvis.d.B.B.a(Z:2256)
at com.onseven.dbvis.d.B.F$A.call(Z:278)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

Have you been able to overcome this issue?
 
Thanks

devashishbcs 1 post Joined 07/13
17 Jul 2013

Has anybody been able to find the root-cause or the solution to this problem??
I am also affected and afflicted by the same error, in AquaData Studio (that I am using to connect to Teradata), and have been unable to find a resolution for it / a solution to it.
 
 

tomnolan 594 posts Joined 01/08
18 Jul 2013

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
15 Aug 2013

We are having this problem for some time. Any luck guys? i just posted the error we are seeing on new thread.

tomnolan 594 posts Joined 01/08
15 Aug 2013

Yes, thank you for posting to a new thread. Please do not reuse old threads.
 
I replied to your new post: http://forums.teradata.com/forum/connectivity/connection-timeout-problem-driver-version-13-10#comment-79262

You must sign in to leave a comment.