com.microsoft.sqlserver.jdbc.SQLServerException

Connection reset by peer: socket write error

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 web761

  • Connection reset by peer: socket write error
  • Connection reset by peer: socket write error
  • Connection reset by peer: socket write error
  • Stack trace

    • com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset by peer: socket write error at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(Unknown Source) at com.microsoft.sqlserver.jdbc.TDSChannel.write(Unknown Source) at com.microsoft.sqlserver.jdbc.TDSWriter.flush(Unknown Source) at com.microsoft.sqlserver.jdbc.TDSWriter.writePacket(UnknownSource) at com.microsoft.sqlserver.jdbc.TDSWriter.endMessage(Unknown Source) at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(UnknownSource) at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(UnknownSource) at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(UnknownSource) at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(UnknownSource) at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(UnknownSource) at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(UnknownSource) at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeUpdate(UnknownSource) at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeUpdate(NewProxyPreparedStatement.java:105) at org.apache.activemq.store.jdbc.DefaultDatabaseLocker.keepAlive(DefaultDatabaseLocker.java:118) at org.apache.activemq.store.jdbc.JDBCPersistenceAdapter.databaseLockKeepAlive(JDBCPersistenceAdapter.java:481) at org.apache.activemq.store.jdbc.JDBCPersistenceAdapter$1.run(JDBCPersistenceAdapter.java:183) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619)

    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
    2 times, 1 year ago
    120 times, 1 month ago
    23 times, 2 months ago
    2667 times, 10 months ago
    Unknown user
    Once, 11 months ago
    38 more bugmates