Hello Jeff,

The multiple instance part is interesting.

One option is to use a clustered scheuler.
I have used flux, and it works well.

I think open source Quartz does the trick as well.
http://www.opensymphony.com/quartz/wikidocs/ConfigJDBCJobStoreClustering.html

Alternatively, you could schedule this job on all machine and try to
implement concurrency control which works across JVMs.

The lock - for handling concurrency - is best obtained from a database.
Alternatively, you can make your life more complex and use a file
system and custom code to keep this lock, but be aware that you will
need to check that the OS you are using allows file locking. Java.NIO
lock may not work across JVMs.

Java is quite efficient at listing the files in the file system, so you
are unlikely to run into any issues while polling.

If you have a clustered database - it might be better to create this
job on the database- or trigger it from database - so that it runs only
on one machine and fails over whenever the database does.

Pranshu