Re: Connector/J "Expected to read 4 bytes, read 0 bytes before connection was unexpectedly lost."
Posted by: Jonathan Baxter
Date: October 31, 2008 07:56AM

I have seen a similar problem when streaming large ResultSets.

I managed to fix it with:

net_write_timeout = 3600

(default is 60 seconds).

It seems that if processing a single row from a streaming ResultSet takes longer than net_write_timeout seconds the mysql server closes the Connection (or closes something down), which then causes the next read to barf.

Options: ReplyQuote


Subject
Written By
Posted
Re: Connector/J "Expected to read 4 bytes, read 0 bytes before connection was unexpectedly lost."
October 31, 2008 07:56AM


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.