Huy Le
Mar 31, 2014
  3852
(5 votes)

Job Fails Issue

Here's a short note on a case we had recently, hopefully it might be useful to somebody.

A Partner had an issue with a custom EPiServer scheduled job (commerce import) that failed intermittently on their CMS 7 site, the error message that the job failed with was: "Thread was being aborted."

We suspected that the application was going down and after some pondering a colleague suggested adding this very useful tool to the site Bin folder which logs application shutdown events on the machine’s Window log:

http://epiwiki.se/tools/application-restart-detector

The tool logged the below shutdown event in the Windows logs (Application) on the machine very shortly before the job stopped running.

This was logged many times on the server:

Application restarted because:MaxRecompilationsReached
   at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
   at System.Environment.get_StackTrace()
   at System.Web.Hosting.HostingEnvironment.InitiateShutdownInternal()
   at System.Web.HttpRuntime.ShutdownAppDomain(String stackTrace)
   at System.Web.Compilation.DiskBuildResultCache.ShutdownCallBack(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

We were still unsure what lay behind the error so we added another tool made by the same colleague, though this didn't shed any light on the issue this time:

http://epiwiki.se/tools/asseblyloaderdetector

A couple of colleagues mentioned that there was a recent bug report concerning EPiServer.Web.Hosting.VirtualPathMappedProvider

,which we saw was being used on the site in question.

The ="DynamicContentPreview" VirtualPathMappedProvider was then commented out from the episerverframework config.

After this was commented out the MaxRecompilationsReached error stopped the job has not failed since.

The cause of this issue is covered by this recently reported bug:

Bug #112977: Excessive recompilations causing performance problems

http://world.episerver.com/Documentation/Release-Notes/ReleaseNote/?releaseNoteId=112977

Thanks to all that gave assistance on this case! //Paul & co

Mar 31, 2014

Comments

Vincent
Vincent Apr 1, 2014 03:35 AM

Is EPiServer team going to release a patch for CMS 6R2?

Apr 1, 2014 03:07 PM

@code monkey: could you create a support ticket for this?

Please login to comment.
Latest blogs
Optimizely SendGrid SMTP host is deprecated

SendGrid is a services for sending email that is included in Optimizely DXP. Previously smtp.episerver.net was the recommended SMTP server to use,...

Tomas Hensrud Gulla | Dec 4, 2022 | Syndicated blog

Hosting Optimizely CMS 12 on Docker Engine

Since Optimizely CMS can now be deployed as a Docker container, here is a demonstration of building, running and scaling an Optimizely CMS 12 site ...

Stefan Holm Olsen | Dec 4, 2022 | Syndicated blog

How to use CacheTagHelper with content areas in Optimizely CMS 12

I might be going out on a limb here - if you have a better solution, feel very free to share it!  Upgrading your Optimizely web application from .N...

Andreas J | Dec 2, 2022

The 1001st Piece in your 1000 Piece Puzzle: .NET Default Interface Functions

I was recently working with a client who wanted a reasonably large subsystem added to Optimizely that would add automated management to their...

Greg J | Nov 28, 2022 | Syndicated blog