I have a situation as below which gives me error and looks like timeout. Its missing some insert of records. the error is as below:
IdeaBlade.EntityModel.AsyncProcessor1.<>c__DisplayClass2.<.ctor>b__0(TArgs args)
at IdeaBlade.EntityModel.AsyncProcessor
1.Signal()
at IdeaBlade.EntityModel.AsyncProcessor`1.b__5(Object x)
InnerException: [HttpRequestTimedOutWithoutDetail] Arguments: Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.0.10411.00&File=System.ServiceModel.dll&Key=HttpRequestTimedOutWithoutDetail
at IdeaBlade.EntityModel.EntityServerProxy.<>c_DisplayClass14.b_13()
at IdeaBlade.EntityModel.EntityServerProxy.ExecFunc[T](Func1 func, Boolean funcWillHandleException)
at IdeaBlade.EntityModel.EntityServerProxy.ExecuteOnServer[T](Func
1 func, Boolean funcWillHandleException)
at IdeaBlade.EntityModel.EntityServerProxy.InvokeServerMethod(SessionBundle sessionBundle, ITypeWrapper entityManagerType, String typeName, String methodName, Object[] args)
at IdeaBlade.EntityModel.EntityMa
Any Idea how to handle it? Thx:)
......
.ExecuteAsync(op =>
{
var cust =Customers.Where(p => p.IsSelected).ToList();
..........................
Ships.ForEach(.......
...........
EntityManager.SalesGetSalesQuery(
..............
.ExecuteAsync(opn =>
{
................
});
p.UpdateOrders(copyOrders);
Orders.Add(copyOrders);
Save();
});
A timeout can happen at several places, so you will want to increase all possible timeout values.
In this case, you should be looking at increasing the query (CommandTimeout and Transaction), communication, and IIS executionTimeout.
DevForce has a documentation page that talks about troubleshooting timeouts. It's at http://drc.ideablade.com/devforce-2012/bin/view/Documentation/understand-timeouts.
I noticed that your nested query ("SalesGetSalesQuery") is a StoredProcQuery. There is an outstanding bug where StoredProcQueries are not respecting the Transaction timeout value, if different than the default. (120 seconds) We are working on a fix, but unfortunately there's no workaround in the meantime.
If it's not the StoredProcQuery that's timing out, then the link above will help you resolve it.