| 11/2/2011 (13 years ago) | |
| Clarify | |
| Any | |
| 1/19/2016 (9 years ago) | |
| Windows (Any) | |
| Any |
During FcApplication initialization of the Dovetail SDK (fcSDK), the following error may occur:
System.Threading.ThreadAbortException: Thread was being aborted.
The stack trace may look something like:
[ERROR] [FChoice.Foundation.FCApplication] Error initializing CacheManager and LicenseManager: Thread was being aborted. [user: (null)] [sessionid: (null)]
System.Threading.ThreadAbortException: Thread was being aborted.
at FChoice.Common.Data.SqlHelper.FillDataSet(DbDataAdapter adapter, DataSet ds, String tableNames, IDbConnection connection, CommandType cmdType, String cmdText, DataParameterCollection dataParams, Boolean fillSchema)
at FChoice.Common.Data.SqlHelper.FillDataSet(DataSet ds, String tableNames, IDbConnection conn, CommandType cmdType, String cmdText, DataParameterCollection dataParams, Boolean fillSchema)
at FChoice.Common.Data.SqlHelper.FillDataSet(DataSet ds, String sqlStmt, String tableNames, Boolean fillSchema)
at FChoice.Common.Data.SqlHelper.FillDataSet(DataSet ds, String sqlStmt, String tableNames)
at FChoice.Foundation.Clarify.StringCache.LoadStringTable(DataSet stringDs)
at FChoice.Foundation.Clarify.StringCache.InitCacheData()
at FChoice.Foundation.CacheBase.InitializeCache()
at FChoice.Foundation.CacheManager.LoadDataCaches(CacheBase caches)
at FChoice.Foundation.CacheManager.Initialize(CacheBase caches, ISchemaCache schemaMaster)
at FChoice.Foundation.FCApplication.FCAppInitialize(CacheBase caches, ISchemaCache schemaMaster)
2011-11-01 18:31:34,237 [ERROR] [FChoice.Common.Data.SqlHelper] Error while performing a FillDataSet database command [user: (null)] [sessionid: (null)]
System.Threading.ThreadAbortException: Thread was being aborted.
at System.Data.Common.UnsafeNativeMethods.OCIStmtFetch(OciHandle stmtp, OciHandle errhp, UInt32 nrows, FETCH orientation, MODE mode)
at System.Data.OracleClient.TracedNativeMethods.OCIStmtFetch(OciHandle stmtp, OciHandle errhp, Int32 nrows, FETCH orientation, MODE mode)
at System.Data.OracleClient.OracleDataReader.ReadInternal()
at System.Data.OracleClient.OracleDataReader.Read()
at System.Data.Common.DataAdapter.FillLoadDataRow(SchemaMapping mapping)
at System.Data.Common.DataAdapter.FillFromReader(DataSet dataset, DataTable datatable, String srcTable, DataReaderContainer dataReader, Int32 startRecord, Int32 maxRecords, DataColumn parentChapterColumn, Object parentChapterValue)
at System.Data.Common.DataAdapter.Fill(DataSet dataSet, String srcTable, IDataReader dataReader, Int32 startRecord, Int32 maxRecords)
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable)
at FChoice.Common.Data.SqlHelper.FillDataSet(DbDataAdapter adapter, DataSet ds, String tableNames, IDbConnection connection, CommandType cmdType, String cmdText, DataParameterCollection dataParams, Boolean fillSchema)
If the code executing on the thread (including the Dovetail SDK Application Initialization) is taking too long, ASP.NET can abort the thread, which means the SDK doesn’t get fully initialized. This may cause further downstream errors such as the inability to create a session (FCSession, ClarifySession).
One way to tackle this is to tweak your timeout settings.
When hosting a web service, there is some process monitoring how long a web service call is taking. If a call is taking too long, then it is killed and a ThreadAbortException will occur. The timeout can be increased by a setting in the web.config file.
For a web service hosted in ASP.NET, the configuration property is executionTimeout:
<configuration>
<system.web>
<httpRuntime executionTimeout="360" />
</system.web>
</configuration>
For a web service running outside of ASP.NET, e.g. hosted as soap.tcp, the configuration property is executionTimeoutInSeconds:
<configuration>
<microsoft.web.services3>
<messaging>
<executionTimeoutInSeconds value="360" />
</messaging>
</microsoft.web.services3>
</configuration>
Add the appropriate setting to your web.config file and re-test.
While this may cause the application to initialize, increasing the timeout may mask the true underlying issue. Root cause analysis would be useful here.
In one particular instance, there were a few database queries that were taking an extremely long time during the SDK initialization process, indicating a database performance/tuning issue. Further investigation of query performance and proper database tuning is recommended.
You must be logged in to post a comment.
Login