Vulnerability in EPiServer.Forms

Try our conversational search powered by Generative AI!

DB deadlocks involving DemoXFromsPostsGeneratorJob, loadbalanced

Vote:
 

Hello fellow EPiServians

I've upgraded a 4.62 solution to 6.0 some time ago, and it seems to run OK. Now, our database admin have bought a new survailance tool for the database server and have descovered deadlocks at random intervals between 3 and 20 minutes. He send me a trace and if i'm rading the trace info right, this is the two calls that give the deadlock:

10 Mar 2011 13:38:29exec netSchedulerExecute @pkID='79833BD4-56D0-46C6-95BD-B436A70C4A80',@nextExec='Mar 10 2011 12:38:26:203PM',@utcnow='Mar 10 2011 12:38:29:660PM'

10 Mar 2011 13:38:29exec netSchedulerExecute @pkID='79833BD4-56D0-46C6-95BD-B436A70C4A80',@nextExec='Mar 10 2011 12:38:26:203PM',@utcnow='Mar 10 2011 12:38:31:327PM'

I've looked up the job name to be DemoXFromsPostsGeneratorJob. It executes every 5 seconds.

DB admins don't like deadlocks as they cost performance, but once in a while are ok. In our case, we have the website hosted on two webservers with one database. This means we have two schedulers running at therefor we have this performance issue.

Well, on to my question: What is the perpose of DemoXFromsPostsGeneratorJob? We don't use XForms, so is it OK to disable it? Is it a leftover from episerver 4?

#49267
Mar 10, 2011 14:52
Vote:
 

Hi

I am not fully aware of the background of that job. When I look in the source code I can see that it used from the XFormsViewer gadget, probably it is used from the gadget to generate som kind of data.

Anyway it should be perfectly fine to disable it.

#49273
Mar 11, 2011 7:30
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.