R – Quartz.Net Thread Pools

netquartz-schedulerquartz.net

I have quartz.net set up to run several scheduled jobs and several polling jobs. The polling jobs can consist of running code that can take 10 minutes. These jobs are queued from user actions (and so there could be a queue of x user actions).
I have scheuled jobs that HAVE to run at that time. However, the threads could all be used up by the long running polling jobs. Is there any way to have a designated thread for the scheduled tasks that will never be used by the polling jobs?

I am aware of the thread priority but this will not guarentee the scheduled job will run if the other threads are already in use.

Thanks for any help.

Best Answer

Another suggestion, when the job fires, spin another thread off to do the work, so you can return the job thread to the Quartz pool.

Use a bounded thread pool for the worker threads, so you don't get too many worker threads running at the same time.

See, java.util.concurrent for the Executor and ThreadPool classes. It's a more complicated solution, but may scale better.

Related Solutions

C# – How to update the GUI from another thread

The simplest way is an anonymous method passed into Label.Invoke:

// Running on the worker thread
string newText = "abc";
form.Label.Invoke((MethodInvoker)delegate {
    // Running on the UI thread
    form.Label.Text = newText;
});
// Back on the worker thread

Notice that Invoke blocks execution until it completes--this is synchronous code. The question doesn't ask about asynchronous code, but there is lots of content on Stack Overflow about writing asynchronous code when you want to learn about it.

C# – What does a lock statement do under the hood

The lock statement is translated by C# 3.0 to the following:

var temp = obj;

Monitor.Enter(temp);

try
{
    // body
}
finally
{
    Monitor.Exit(temp);
}

In C# 4.0 this has changed and it is now generated as follows:

bool lockWasTaken = false;
var temp = obj;
try
{
    Monitor.Enter(temp, ref lockWasTaken);
    // body
}
finally
{
    if (lockWasTaken)
    {
        Monitor.Exit(temp); 
    }
}

You can find more info about what Monitor.Enter does here. To quote MSDN:

Use Enter to acquire the Monitor on the object passed as the parameter. If another thread has executed an Enter on the object but has not yet executed the corresponding Exit, the current thread will block until the other thread releases the object. It is legal for the same thread to invoke Enter more than once without it blocking; however, an equal number of Exit calls must be invoked before other threads waiting on the object will unblock.

The Monitor.Enter method will wait infinitely; it will not time out.

Best Answer

Related Solutions

C# – How to update the GUI from another thread

C# – What does a lock statement do under the hood

Related Topic