Hi
I just got "I/O Error: Connection reset by peer: socket write error" when running an overnight job. I researched the problem on the internet and it seems its probably caused by many concurrent users on MS SQL Server confusing Java that socked was closed. Did anything similar happened to anyone in the community?
OS: Win7; DB: Microsoft SQL Server 2008.
Error message:
connecting to socket on port 4030
connected
I/O Error: Connection reset by peer: socket write error
Exception in component tMSSqlOutput_2
java.sql.SQLException: Invalid state, the Connection object is closed.
at net.sourceforge.jtds.jdbc.TdsCore.checkOpen(TdsCore.java:448)
at net.sourceforge.jtds.jdbc.TdsCore.clearResponseQueue(TdsCore.java:723)
at net.sourceforge.jtds.jdbc.JtdsStatement.initialize(JtdsStatement.java:586)
at net.sourceforge.jtds.jdbc.JtdsStatement.executeBatch(JtdsStatement.java:851)
at undq.test_fuzzy_trigram_without_joins_0_1.TEST_fuzzy_trigram_without_joins.tMSSqlInput_3Process(TEST_fuzzy_trigram_without_joins.java:3741)
at undq.test_fuzzy_trigram_without_joins_0_1.TEST_fuzzy_trigram_without_joins.runJobInTOS(TEST_fuzzy_trigram_without_joins.java:5298)
at undq.test_fuzzy_trigram_without_joins_0_1.TEST_fuzzy_trigram_without_joins.main(TEST_fuzzy_trigram_without_joins.java:5172)
disconnected
Job TEST_fuzzy_trigram_without_joins ended at 20:50 30/06/2010.