Quantcast
Channel: Using Optimizely Platforms
Viewing all articles
Browse latest Browse all 8020

[Thread was being aborted] for long running scheduled jobs

$
0
0

We use scheduled jobs to handle many tasks on our platform (Catalog indexing, product imports, site maps, etc.). Some of these scheduled jobs run for a long time (up to 5-6 hours). 

The last few months, these jobs fail with "Thread was being aborted" in the Episerver Scheduled jobs UI. They are scheduled to run every night, and I would say that they fail in about 8 out of 10 runs.

I have done the following things to try and solve this:

  • Deactivate CPU and memory limit on the CMS and Commerce application pools.
    • In advanced settings set CPU limit to 0 and Private Memory limit to 0.
  • Set start mode of all app pools to "AlwaysRunning"
  • Verified that no app pool recycles is made during the run of the job.
  • Verified that the server does not run out of CPU or Memory.
  • Set up a script using curl to request the site every five minutes.

Any tips on how to resolve this issue is greatly appreciated!


Viewing all articles
Browse latest Browse all 8020

Trending Articles