Sandbox Solution Timeout for SharePoint 2010

Question

Is there a way to configure a timeout value for a solution for a SharePoint 2010 sandbox? I think it defaults to 30 seconds. I have a web part that sometimes takes a little longer. I would prefer not to return to the farming solution if I can avoid it.

Answer 1

Finding documentation on this was a bit difficult, but I found it here . Here are some of them:

For a request with a request, it foams : there is a strict limit on how long an isolated solution can be executed. The default is 30 seconds. If the sandboxed solution exceeds the limit, the application domain that processes the request (but not the sandboxed workflow) is terminated. This limit is customizable, but only through custom code for the object model. It is not possible to access the corresponding parts of the object model using isolated solutions, so no isolated solution can change the limit.

Processor Runtime The absolute limit of this resource is not applicable if it is set higher than Per Request, with the above query foaming limit. Typically, administrators want to keep it higher so that a slow request is interrupted before it completes the entire isolated workflow, including even well-executed isolated solutions that work in it.

The following code can be used to configure the request timeout:

SPUserCodeService.Local.WorkerProcessExecutionTimeout = 40; SPUserCodeService.Local.Update(); 

You should be able to configure the CPU runtime as follows:

 SPUserCodeService.Local.ResourceMeasures["CPUExecutionTime"].AbsoluteLimit = 50.0; SPUserCodeService.Local.Update(); 

For the changes to take effect, you must restart the Microsoft SharePoint Foundation Text Code service.

Answer 2

In PowerShell, you can configure timeouts using the following commands:

 $uc=[Microsoft.SharePoint.Administration.SPUserCodeService]::Local $uc.WorkerProcessExecutionTimeout = 60 $uc.ResourceMeasures["CPUExecutionTime"].AbsoluteLimit = 120 $uc.Update()