Page 1 of 1

Error socket not connected

Posted: Fri 04 Mar 2011 03:38
by alfrye
I have a c stored procedure that accepts a bytea parameter that reads the bytes in write them to the file system. everything works correctly as long as the file I am reading in is less than 2 MB. When the source file is larger than 2 mb I immediatly get the socket not connected error and non of my stored procedure code runs. I have tried using the dotconnect for LINQ and the standard dotconnect and both give same result. I jave also tried changing the connection and command timeout time and either seem to help!

Thanks,
Alan

Socket not connected

Posted: Fri 04 Mar 2011 14:36
by alfrye
Here is the call stack

at Devart.Data.PostgreSql.PgSqlDataReader.e(Int32 A_0)
at Devart.Data.PostgreSql.PgSqlCommand.InternalExecute(CommandBehavior behavior, IDisposable stmt, Int32 startRecord, Int32 maxRecords)
at Devart.Common.DbCommandBase.InternalExecute(CommandBehavior behavior, IDisposable stmt, Int32 startRecord, Int32 maxRecords, Boolean nonQuery)
at Devart.Common.DbCommandBase.ExecuteDbDataReader(CommandBehavior behavior, Boolean nonQuery)
at Devart.Common.DbCommandBase.ExecuteDbDataReader(CommandBehavior behavior)
at System.Data.Common.DbCommand.ExecuteReader()
at Devart.Common.DbCommandBase.ExecuteNonQuery()
at UnitTests.RtacCommonDataProviderTest.UpgradeHMIRuntimeTest()

Socket not connected

Posted: Fri 04 Mar 2011 21:56
by alfrye
I was able able to track down my issue and it was a code error in the c stored procedure. Once this was correct everything started working as expected.