Best unofficial Apache Server developers community |
|
I have a server with multiple Tomcat instances and each contains about 10 application contexts. I am considering using Quartz for some scheduling requirements we currently received. I first thought that one Quartz server running and servicing all of the scheduling requests for each instance would be best, however it seems that most of the user guides bundle Quartz with each application. My scheduler will have to run jobs on different databases for different contexts. Does anyone out there have a similar set up? Can anyone recommend how to use Quartz efficiently in the multiple instance, multiple context set up? Will bundling a separate scheduler with each web app significantly increase the hardware resources I will need? Any general advice? Thank you.
posted via StackOverflow
|