java.sql.SQLException: Out of memory (mysql-java connector 3.1.12)
Posted by: Aijaz Syed
Date: February 28, 2006 02:40PM

Hi,

I am having a wierd problem when I am using MySQL Java Connector 3.1.12, I dont not have this problem for 3.0.10 stable version.

Server A (some application server A): Using MySQL 5.0.18, for apple-darwin8.2.0 on powerpc; and JDBC Connector used is 3.1.12. Trys to connect to Database server to and perform some operations.

Server B (application server A): Using MySQL 4.1.13a, for apple-darwin8.0 on powerpc; and JDBC Connector used is 3.0.10. Trys to connect to Database server to and perform some operations.

The Database Server for aforementioned applications in on Server B. Server A and Server B are physically different machines with same computational power and with same JVM.

I always end up getting the following error on Server A and never on Server B,
the problem is with MySQL server/Driver as the computational power, application and JVM are same:

java.sql.SQLException: Out of memory (Needed 2020 bytes)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2928)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1571)
at com.mysql.jdbc.ServerPreparedStatement.serverExecute(ServerPreparedStatement.java:1124)
at com.mysql.jdbc.ServerPreparedStatement.executeInternal(ServerPreparedStatement.java:676)
at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1030)
at rehab.server.BlastLongJob.addHitsForSequence(BlastLongJob.java:997)
at rehab.server.BlastLongJob.parseXMLfiles(BlastLongJob.java:712)
at rehab.server.BlastLongJob.doWork(BlastLongJob.java:369)
at rehab.server.BlastLongJob.run(BlastLongJob.java:192)
com.mysql.jdbc.CommunicationsException: Communications link failure due to underlying exception:

** BEGIN NESTED EXCEPTION **

java.io.EOFException

STACKTRACE:

java.io.EOFException
at com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:1905)
at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:2351)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2862)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1571)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1666)
at com.mysql.jdbc.Connection.execSQL(Connection.java:2994)
at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:936)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1166)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1082)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1067)
at rehab.server.BlastLongJob.parseXMLfiles(BlastLongJob.java:719)
at rehab.server.BlastLongJob.doWork(BlastLongJob.java:369)
at rehab.server.BlastLongJob.run(BlastLongJob.java:192)


** END NESTED EXCEPTION **

I was trying to see how the memory management was for Server A (not the MySQL server) which is using newer java connector (3.1.12), I was seeing a steady increase. Where as with Server B it was almost constant.

Can I have any lead so as to why I get this is happening?

Options: ReplyQuote


Subject
Written By
Posted
java.sql.SQLException: Out of memory (mysql-java connector 3.1.12)
February 28, 2006 02:40PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.