Sql server connection reset

We are facing a connection reset issue while connecting to Dremio. I have exhausted all the other options and hence putting my issue here.

@yeshreddy

What is the error you are getting? Can you please post server.log?

Thanks
Bali

Hi @balaji.ramaswamy,

This is the error we are seeing:

[Error Id: 1dd3fb36-d641-4e96-b9de-f6c426ad790f on 10.113.131.30:0]

(com.microsoft.sqlserver.jdbc.SQLServerException) Connection reset
com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError():234
com.microsoft.sqlserver.jdbc.SimpleInputStream.getBytes():352
com.microsoft.sqlserver.jdbc.DDC.convertStreamToObject():796
com.microsoft.sqlserver.jdbc.ServerDTVImpl.getValue():3777
com.microsoft.sqlserver.jdbc.DTV.getValue():247
com.microsoft.sqlserver.jdbc.Column.getValue():190
com.microsoft.sqlserver.jdbc.SQLServerResultSet.getValue():2053
com.microsoft.sqlserver.jdbc.SQLServerResultSet.getValue():2039
com.microsoft.sqlserver.jdbc.SQLServerResultSet.getString():2508
com.dremio.exec.store.jdbc.JdbcRecordReader$VarCharTrimCopier.copy():590
com.dremio.exec.store.jdbc.JdbcRecordReader.next():251
com.dremio.exec.store.CoercionReader.next():200
com.dremio.sabot.op.scan.ScanOperator.outputData():248
com.dremio.sabot.driver.SmartOp$SmartProducer.outputData():521
com.dremio.sabot.driver.StraightPipe.pump():56
com.dremio.sabot.driver.Pipeline.doPump():109
com.dremio.sabot.driver.Pipeline.pumpOnce():99
com.dremio.sabot.exec.fragment.FragmentExecutor$DoAsPumper.run():336
com.dremio.sabot.exec.fragment.FragmentExecutor.run():285
com.dremio.sabot.exec.fragment.FragmentExecutor.access$1200():92
com.dremio.sabot.exec.fragment.FragmentExecutor$AsyncTaskImpl.run():679
com.dremio.sabot.task.AsyncTaskWrapper.run():112
com.dremio.sabot.task.slicing.SlicingThread.mainExecutionLoop():226
com.dremio.sabot.task.slicing.SlicingThread.run():156

We are getting this error even though there is no timeout set from sql server database. The connection gets reset at random intervals and we couldnot understand what could be the problem

@yeshreddy

Have you set an idle timeout connection property for this user on the SQL server side?