Give each instance it's own instanceId in general.properties and everything should be fine. The JobManager periodically polls looking for jobs that aren't assigned, queued or cancelled and then assigns them to its instance using the instanceId and queues them.
It would probably take me as long to explain fully as it would for you to just go to the JobManager.poll() method and have a look at it :-) Regards Scott HotWax Media http://www.hotwaxmedia.com On 21/07/2010, at 12:27 PM, Craig Ambrose wrote: > I have a multiple instance deployment backed by a single database. I have a > user-triggered event that creates a JobSandbox entry that is to execute a > week in the future. Is it (reasonably) guaranteed that the job will only be > executed by a single instance? It would be bad for our customers if the job > is executed by more than one of the instances. > > Can anyone shed some light on what mechanism is responsible for ensuring that > only one runtime instance will execute a certain job? > > Thanks > > -craig >
smime.p7s
Description: S/MIME cryptographic signature
