java.sql.SQLException

Insufficient data while reading from the network - expected a minimum of 6 bytes and received on y -1 bytes. The connection has been terminated.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web13993

  • via Apache's JIRA Issue Tracker by Oliver Seidel, 10 months ago
    Insufficient data while reading from the network - expected a minimum of 6 bytes and received on y -1 bytes. The connection has been terminated.
  • via Apache's JIRA Issue Tracker by Jason C. Cole, 1 year ago
    A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message
  • A network protocol error was encountered and the connection has been terminated: the requested command encountered an unarchitected and implementation-specific condition for which there was no architected message
  • Stack trace

    • java.sql.SQLException: Insufficient data while reading from the network - expected a minimum of 6 bytes and received on y -1 bytes. The connection has been terminated. at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(SQLExceptionFactory.java:46) at org.apache.derby.client.am.SqlException.getSQLException(SqlException.java:362) at org.apache.derby.client.am.PreparedStatement.executeUpdate(PreparedStatement.java:391) at error.fill_db(error.java:147) at error.main(error.java:171) Caused by: org.apache.derby.client.am.DisconnectException: Insufficient data while reading from the network - expected minimum of 6 bytes and received only -1 bytes. The connection has been terminated. at org.apache.derby.client.net.Reply.fill(Reply.java:195) at org.apache.derby.client.net.Reply.ensureALayerDataInBuffer(Reply.java:215) at org.apache.derby.client.net.Reply.readDssHeader(Reply.java:317) at org.apache.derby.client.net.Reply.startSameIdChainParse(Reply.java:1147) at org.apache.derby.client.net.NetStatementReply.readExecute(NetStatementReply.java:69) at org.apache.derby.client.net.StatementReply.readExecute(StatementReply.java:55) at org.apache.derby.client.net.NetPreparedStatement.readExecute_(NetPreparedStatement.java:183) at org.apache.derby.client.am.PreparedStatement.readExecute(PreparedStatement.java:1796) at org.apache.derby.client.am.PreparedStatement.flowExecute(PreparedStatement.java:2116) at org.apache.derby.client.am.PreparedStatement.executeUpdateX(PreparedStatement.java:396) at org.apache.derby.client.am.PreparedStatement.executeUpdate(PreparedStatement.java:382) ... 2 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown user
    Once, 11 months ago