recurring java.il.EOFException in mysql driver

From: Robert Zeigler (robert..uregumption.com)
Date: Fri Nov 30 2007 - 16:27:31 EST

  • Next message: Andrus Adamchik: "Re: recurring java.il.EOFException in mysql driver"

    I have several webapps running some version of tapestry + cayenne,
    with mysql as the backend. Intermittently, I get an exception along
    the lines of:

    org.apache.cayenne.CayenneRuntimeException: [v.2.0-SNAPSHOT March 30
    2007] Global exception.
            at
    org
    .apache
    .cayenne
    .access
    .DataDomainQueryAction.nextGlobalException(DataDomainQueryAction.java:
    432)
            at org.apache.cayenne.access.DataNode.performQueries(DataNode.java:261)
             ...

    Caused by:

    java.io.EOFException
            at com.mysql.jdbc.MysqlIO.readFully(MysqlIO.java:1934)
            at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:2380)
            at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2909)
            at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1600)
            at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1695)
            at com.mysql.jdbc.Connection.execSQL(Connection.java:3020)
            at com.mysql.jdbc.Connection.setAutoCommit(Connection.java:4989)
            at
    org
    .apache
    .cayenne
    .conn.PooledConnectionImpl.getConnection(PooledConnectionImpl.java:133)
             ...

    with a bit of follow up:
    Last packet sent to the server was 2 ms ago.
            at com.mysql.jdbc.MysqlIO.reuseAndReadPacket(MysqlIO.java:2592)
            at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2909)
             ...

    Now, while I'm normally inclined to chalk weird errors up to some
    weirdness in my code, and start digging, in this case, I'm scratching
    my head. I've seen this now on three different servers (all running
    linux) and in at least three independent (except for the dependence on
    cayenne) applications. So I'm sitting here wondering: has anybody
    else seen this?? If not, I'll chalk it up to a bug (threading
    issues?), and start hunting. ;)

    Thanks!

    Robert



    This archive was generated by hypermail 2.0.0 : Fri Nov 30 2007 - 16:28:18 EST