1. Andres Slachevsky
  2. PowerServer 2020 or older (Obsolete)
  3. Monday, 28 May 2018 12:40 PM UTC

I have and store procedure in MS SQL Server

Running the procedure from the PB Client Server application it takes 20-25 Minutes to RUN

i have change all the TimeOut Settings to 3600 Seconds (both in the application ->transaction-> Timeout and the the Data Cache Setting)
 

around 10 minutes running the procedure i get this error

 

 

error_timeout

 

In the Appeon server log i have this:

 

2018-05-28 08:34:14.877 : Thread was being aborted.
   at SNIReadSyncOverAsync(SNI_ConnWrapper* , SNI_Packet** , Int32 )
   at SNINativeMethodWrapper.SNIReadSyncOverAsync(SafeHandle pConn, IntPtr& packet, Int32 timeout)
   at System.Data.SqlClient.TdsParserStateObject.ReadSniSyncOverAsync()
   at System.Data.SqlClient.TdsParserStateObject.TryReadNetworkPacket()
   at System.Data.SqlClient.TdsParserStateObject.TryPrepareBuffer()
   at System.Data.SqlClient.TdsParserStateObject.TryReadByte(Byte& value)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
   at System.Data.SqlClient.SqlDataReader.get_MetaData()
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader()
   at Appeon.Server.Services.DataService.Sql.EonSqlCommand.ExecuteReader()
   at Appeon.Server.Services.DataService.EonDbCommand.ExecuteCursor(SQLType sqlType, String sql)
   at Appeon.Server.Commands.EmbedSQLCommand.ExecuteCommand()
   at Appeon.Server.Commands.EmbedSQLCommand.Execute()
   at Appeon.Server.Commands.Command.ConstructAndExecute(CommandData commandData)
   at Appeon.Server.Services.Controller.JRouterImpl.ExecuteInTransaction(CommandData commandData)
   at Appeon.Server.Services.Controller.JRouterImpl.ExecuteCommand(HttpResponse response, CommandData superCommand, SessionAccessInfo session)
   at Appeon.Server.Services.Controller.JRouterImpl.Call(Int32 clientType, Object requestData, Hashtable clientContext, String& outPutStream_Key)
2018-05-28 08:34:14.893 : Thread was being aborted.
   at SNIReadSyncOverAsync(SNI_ConnWrapper* , SNI_Packet** , Int32 )
   at SNINativeMethodWrapper.SNIReadSyncOverAsync(SafeHandle pConn, IntPtr& packet, Int32 timeout)
   at System.Data.SqlClient.TdsParserStateObject.ReadSniSyncOverAsync()
   at System.Data.SqlClient.TdsParserStateObject.TryReadNetworkPacket()
   at System.Data.SqlClient.TdsParserStateObject.TryPrepareBuffer()
   at System.Data.SqlClient.TdsParserStateObject.TryReadByte(Byte& value)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
   at System.Data.SqlClient.SqlDataReader.get_MetaData()
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader()
   at Appeon.Server.Services.DataService.Sql.EonSqlCommand.ExecuteReader()
   at Appeon.Server.Services.DataService.EonDbCommand.ExecuteCursor(SQLType sqlType, String sql)
   at Appeon.Server.Commands.EmbedSQLCommand.ExecuteCommand()
   at Appeon.Server.Commands.EmbedSQLCommand.Execute()
   at Appeon.Server.Commands.Command.ConstructAndExecute(CommandData commandData)
   at Appeon.Server.Services.Controller.JRouterImpl.ExecuteInTransaction(CommandData commandData)
   at Appeon.Server.Services.Controller.JRouterImpl.ExecuteCommand(HttpResponse response, CommandData superCommand, SessionAccessInfo session)
   at Appeon.Server.Services.Controller.JRouterImpl.Call(Int32 clientType, Object requestData, Hashtable clientContext, String& outPutStream_Key)
2018-05-28 08:34:14.893 : Thread was being aborted.
   at Appeon.Server.Services.Controller.JRouterImpl.Call(Int32 clientType, Object requestData, Hashtable clientContext, String& outPutStream_Key)
   at Appeon.WebLibrary.AXDispatcher.Page_Load(HttpContext Context)
Roland Smith Accepted Answer Pending Moderation
  1. Monday, 28 May 2018 14:31 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

Running a stored procedure that takes that long from any client is not a good idea. You need to find a way to run it in a background thread or by a scheduler.

Comment
There are no comments made yet.
Appeon Support Team Accepted Answer Pending Moderation
  1. Tuesday, 29 May 2018 00:45 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 2

Hi Andres,

Please refer to the article below to solve the Appeon Communication layer error.
http://support.appeon.com/index.php?/Knowledgebase/Article/View/49/0/how-to-resolve-the-error-occurred-in-the-appeon-communication-layer-only-for-the-iis-server

Regards,
ZhaoKai

Comment
  1. Andres Slachevsky
  2. Tuesday, 29 May 2018 12:04 PM UTC
I have changed all the values in the solution 1



now i have try the solution 1 and i get this error



Origen de configuración:



  205:



  206:



  207:



 



i will remove the extra line and edit the line 206

  1. Helpful
  1. Andres Slachevsky
  2. Tuesday, 29 May 2018 12:20 PM UTC
I can Confirm that the solution 1 solve the problem 



just need to change the executionTimeout

  1. Helpful
  1. Appeon Support Team
  2. Wednesday, 30 May 2018 01:52 AM UTC
Glad to hear that.

  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.