Re: Customer Question - Sasha Pachev - com.mysql.lists.mysql

3 messages in com.mysql.lists.mysqlRe: Customer Question

From	Sent On	Attachments
Andrew Lanthier	11 Oct 1999 10:30
"Terrence W. Zellers"	11 Oct 1999 20:33
Sasha Pachev	11 Oct 1999 20:50

Subject:	Re: Customer Question
From:	Sasha Pachev (sas...@freeservers.com)
Date:	10/11/1999 08:50:37 PM
List:	com.mysql.lists.mysql

Andrew Lanthier wrote:

I am working with a MySQL customer who has a big JDBC MySql application with a re-curring problem.

The problem is that they get an intermitent socket related error in a threaded JDBC application. The error occurs and screws up the open transaction but then the next one goes thru. This is odd in that they open all database connections up front, prepare a bunch of statements, and do not re-connect on an error.

Here is the message:

E0610 Error in executeQuery() E0606 executeQuery() error -- E0701 Error in getResult(). E0112 read() - java.sql.SQLException: E0102 Socket stream was closed in while read was incomplete.

E0609 Error in executeUpdate() E0602 Error in executeUpdate() -- E0701 Error in getResult(). E0112 read() - java.sql.SQLException: E0102 Socket stream was closed in while read was incomplete.

Any thoughts ? Is there documentation on the MySQL error codes?

This is Linux and MySQL 3.22.xx ( I will go and check my self when I visit ). I cannot reproduce this on 3.22.16.

As an ex vendor I realize this is not alot of info to go on. But some direction on how to get to this level of info for MYSQL will be appreciated.

I do not work very much with JDBC, so maybe someone else who does might be able to tell you exactly what is wrong. However, I would suggest a couple of things:

- bug your client so that you can shell get access to his MySQL server - show variables - show extentned status - enable loggining on MySQL and check what query the error happens on - is the error persistent or does it happen only once in a while under some strange conditions? - see if there is anything cool in the error log