Workflow Soluiton

 View Only
  • 1.  Workflow application error : Thread was being aborted

    Posted Jun 27, 2013 08:41 AM

    I  have a workflow which is aborting from the process after 5-10 minutes:

    It's not the same place in the workflow each time, very random, depending on how long each component take.

    Only happens in embedde models. 

    Any seen similar behavior and found a solution ?

    Error message from log:

    Error,27. juni 2013 13:57:04,System.Threading.ThreadAbortException: Thread was being aborted.
       at LogicBase.Core.ExecutionEngine.AbstractExecutionEngine.RunComponent(TLExecutionContext context, IData data, IOrchestrationComponent comp)
       at LogicBase.Core.ExecutionEngine.AbstractExecutionEngine.RunEngine(List`1 executionQueue)

     



  • 2.  RE: Workflow application error : Thread was being aborted
    Best Answer

    Posted Jul 02, 2013 03:12 PM

    Enter the following line of code just after the <system.web> and before the </system.web> lines in the web.config file for the project (if you don't already have an <httpRuntime section in the web config).

    <httpRuntime executionTimeout="xx"/>

    - where "xx" is an integer value in seconds. Then re-publish your project and do an IIS Reset and a restart of the server extensions.

    The default IIS executionTimeout for ASP.NET applications is "110", or just under two minutes. I had an AutoStart Workflow project that was giving me the same error when it attempted to start so I bumped up the executionTimeout value to "300" (5 minutes) and it runs without any issues now. Keep in mind this works fine for me in this project because at the start of the process there is no user interaction. You may not want to do this if the embedded models timing out in your process are between points of user interaction.

     



  • 3.  RE: Workflow application error : Thread was being aborted

    Posted Jul 11, 2013 03:11 AM

    This solves my problems.

    I took a bit different approach to configure it.

    I published my project and changed the executiontimeout in the specific web.config file for the published project. This is done due the long runtime of the process, which is 45 minutes to one hour, and wouldn't have all other projects to have this long timeout time.

    Thanks for the input smiley