Who here is happy with Quartz.Net?

[Timetheos]

Of course, discussions/forums tend to be around pain points, not about
the good. I'm thinking about using it for a project (+future); if I
only see the bad, I'm not likely to use it, correct?

So what do you think? Are you using it? If you had to do it again,
would you select it? If not, what would you use instead? Would you
try to write your own?

Let's hear some of the good, if any.

Thanks,
Tim

[Marko Lahma]

As I might be a bit biased on the subject I won't comment myself, but
I'd like to remind that if anyone has a large deployment of Quartz.NET
inside a product or a project (and better yet happy with it) I would
be more than add a reference to the web page. As we know usually these
are hard to find as NDAs might prevent information sharing.

-Marko

> --
> You received this message because you are subscribed to the Google Groups "Quartz.NET" group.
> To post to this group, send email to quar...@googlegroups.com.
> To unsubscribe from this group, send email to quartznet+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/quartznet?hl=en.
>
>

[Pradeep Bohra]

Well, I have been using it for some time now and i am now used to this quartz scheduler..can't think of my app running without it !

 

I recommend using in your project.It's real simple and quick !!

./Pradeep

[Daniel Bryars]

We integrated Quartz.Net into our tennanted hosted platform a few
weeks ago (to replace our own rolled solution), and haven't looked
back. We use it to schedule "reports", "import jobs" - like getting an
FTP file at a specific time and importing it into our database, "adhoc
C# scripts", and also for running "automation tests" against our
system to make sure it's running correctly.

We have a desktop tool which allows our users can make a "trigger" and
then connect a "Job" (like running a report, a selenium script,
workflow, ftp import etc) and then publish this to the hosted site.

We considered using the built in Windows Task Scheduler (much improved
in Server 2008) or Quartz.Net. Quartz.Net "won" because we need a
central store of job information with the actual "Job Runner" residing
on more than one Server for redundancy. If (when) a Job Runner server
fails, the other one just picks up - this is really good.

The object model is well designed, the code is well written, and it's
reasurring to know that "Quartz" itself is has many years development
on it. We got the actual scheduling and job running put togther and
working in a day or so, and the extensibility points in the framework
look like they will deal with any future requirements we might have.
So far we've made a global job listener to update some perf counters
so that IT can monitor what's going on using Zabbix (which I'd like to
submit to the project once we've tidied it up a little.)

We needed a slightly different "model" where 1 trigger could fire more
than one job. We've exposed this functionality to the users by simply
creating multiple triggers (under the covers, our users don't see
this.)

One point which might be worth noting is that we only do a minimal
ammount of work in the "Quartz Job" itself. We have one Quartz Job
which makes a Web Service call to a farm of Servers - the web service
call returns immediately and runs the meat of the "job/task"
asynchronously. This means the we're only really using "Quartz" as a
scheduler, not to run the jobs itself. We did this because we already
had this mechanism in place, and other things can trigger our
"jobs" (like an inbound SMS, Email, FTP file recieved, in bound phone
call, etc).

When a user "publishes" to the platform the operation is performed
under a distributed transaction (using MSDTC) so a user might change
the Quartz Trigger, in the Quartz database, and change some "other
stuff" in one or more other databases in the system. This just worked
off of the bat, no problems and changes in Quartz were included in the
transaction and were rolled back if another step in the "publish"
operation failed. Very cool.

I'd be more than happy to recipricate and put a reference on our site
to Quartz, email me at "danb at Aeriandi dot co dot uk" and I'll sort
it out.

Dan

> > For more options, visit this group athttp://groups.google.com/group/quartznet?hl=en.- Hide quoted text -
>
> - Show quoted text -

[Mark G. Gillen]

Personally I have Quartz.Net running as a Windows Service in a high volume
production environment and it has been flawless. Granted the architecture I
chose to implement is a relatively low number of jobs about 20 and I defer
some of the heavy lifting to asyn calls to WCF or the database. Regardless,
the Quartz scheduler setup via XML was really trivial and makes for a very
pluggable architecture. I can add jobs, adjust threads, and in general I
find the Quartz system to be very flexible.

Most of the issues people seem to raise that I have noticed are in relation
to job schedules and the like. I only use CRON jobs in my implementation
currently which is more of a polling approach with established jobs rather
than spawning jobs programmatically.

Overall I am very pleased and will definitely continue to use Quartz.Net and
upgrade as new production releases become available.

Regards,

Mark G.

[Gary German]

We've been happy with Quartz.Net. We've deployed it on over 50 web servers,
and use it to offload processing from the web server (in our case, IIS).

We run Quartz within a Windows service. When the service starts up, it
starts a repeating job that "phones home" for jobs (via a call to a central
web service) every 10 minutes. Jobs from the web service are scheduled and
executed by the Quartz scheduler.

We've had a few minor problems (e.g., some possible memory leaks, but we're
not sure if those are from Quartz or our jobs). But overall, Quartz.Net has
become a key component in our architecture, and we're planning to roll out
more features and jobs in future.

Gary

-----Original Message-----
From: quar...@googlegroups.com [mailto:quar...@googlegroups.com] On

Thanks,
Tim

--

[Jay Vilalta]

We've been using it for almost 2 years and I can say we're happy with it.
There is definitely room for improvement around the edges but the core
functionality works well. I would definitely suggest giving it a try before
trying to write your own scheduler. We have several schedulers running on
different servers and on some instances we run close to 1000 jobs a day.

-----Original Message-----
From: quar...@googlegroups.com [mailto:quar...@googlegroups.com] On
Behalf Of Timetheos
Sent: Friday, February 25, 2011 8:01 PM
To: Quartz.NET
Subject: [quartznet:2264] Who here is happy with Quartz.Net?

Thanks,
Tim

--

[Karell Ste-Marie]

I would not change my decision, Quartz.NET is a great product and I would use it hindsight or otherwise.

--
You received this message because you are subscribed to the Google Groups "Quartz.NET" group.
To post to this group, send email to quar...@googlegroups.com.
To unsubscribe from this group, send email to quartznet+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/quartznet?hl=en.

--

------------------------------------------------------------
Karell Ste-Marie
CIO - BrainBank Inc

MCP, MCAD, MCSE, ETC

[Esa Vanhanen-Varho]

Hi,

 

I'm currently involved in a project where we are planning a new environment for a customer and one part of the project is to check options for job scheduling - there is a solution in place but it would also require updating to the new enviromnent, so they want to evaluate also alternative solutions.

 

The customer would probably like to see feedback on Quartz.NET - or even better, direct references, which are unfortunately hard to get as you've already said. But are there any fresh positive comments? It would be a great bonus if someone from Finland or the Nordics could provide feedback.

 

Thanks,

Esa

[Tatu Jäppinen]

One that I've been directly involved is we've been using Quartz.Net for a good while now (1+ year) for fund transaction integration/automation. Timer jobs running every few minutes processing new transactions and other jobs reading in fresh data after end of day processing between two systems. I don't recall having a single issue arisen because of Quartz.Net so a happy camper here.

I left the names out on purpose but they shouldn't be that hard to find with some LinkedIn stalking and googling.

 - Tatu

[Ville Häkli]

We have been using Quartz for some time (~4 years, I have personally used it for couple of years) in our manufacturing execution system without any major headaches. Our product is used by multiple customers in Finland (unfortunately cannot give any names).

We use Quartz for example to triggering jobs that create integration messages based on system events. Those jobs can be triggered anywhere between a few seconds and few hours.

On Friday, November 15, 2013 11:44:25 AM UTC+2, Esa Vanhanen-Varho wrote:

[Jonathan Roeder]

Daniel, if you still remember, would you mind speaking more to this:

"One point which might be worth noting is that we only do a minimal amount of work in the "Quartz Job" itself. We have one Quartz Job which makes a Web Service call to a farm of Servers the web service call returns immediately and runs the meat of the "job/task" asynchronously."

Does the Quartz job complete as soon as it fires the async call to your web service farm, or does it poll the web service farm for completion?

The second approach best emulates a normal Quartz job, but it requires polling, and potentially complicated polling, since you are polling a web service farm. Is that something you've accounted for?

It also ties up a Quartz threadpool thread for the duration, which a normal job does, sure, but is sub-optimal in this case since the Quartz job is only polling.

thanks,

jonathan

[Mark Kharitonov]

I was pretty content (not happy) until I peeked into the source code.

Now I am scared.

[manuel gonzales]

Rolled out Quartz last October and it runs flawless. I have it using parallel processing and interacting with web services and haven't had a problem.

[Landon Campbell]

Yep, been using it for the past 4 years without a hitch. My only problem is finding time to upgrade!

---

Date: Thu, 29 Jan 2015 14:15:16 -0800
From: manny.y....@gmail.com
To: quar...@googlegroups.com
Subject: [quartznet:3978] Re: Who here is happy with Quartz.Net?

Rolled out Quartz last October and it runs flawless. I have it using parallel processing and interacting with web services and haven't had a problem.

--
You received this message because you are subscribed to the Google Groups "Quartz.NET" group.

To unsubscribe from this group and stop receiving emails from it, send an email to quartznet+...@googlegroups.com.

To post to this group, send email to quar...@googlegroups.com.

Visit this group at http://groups.google.com/group/quartznet.
For more options, visit https://groups.google.com/d/optout.

[home...@gmail.com]

We are very happy with it.

It's very robust, we use it into a Windows Service.

It handles 10 types of jobs and about 1000 jobs instances per day.

The only problem I had is when I want to run a new job NOW on computer 1 and the job scheduler is on computer 2 and time are not sync between both computers (if computer 1 is soon that computer 2 more than 1 minute then the job will be set as misfired). It lack a methods to run a job "NOW" (without storing a datetime value).

[Aaron Sulwer]

I am currently using Quartz.net in a few of my products.  specifically a prosper.com application I wrote.  works great!  documentation is lacking though, wish that were better!

[Mark Gillen]

I've been using Quartz.net in production for over 4 years now.

It's rock solid, easy to deploy, and easy to maintain.

I've no complaints. It's an outstanding piece of Open Source software and I wouldn't hesitate to recommend to any one needing an enterprise class scheduling system.

Best Regards,
Mark Gillen

[Misael Alberto Monero Thompson]

I'M HAPPY