Hi, We use ActiveMQ and Camel to facilitate distributing jobs (JMS messages) from a master to multiple workers. We have to support the ability to reliably abort these running jobs. Currently, when our master gets an abort request, it simply broadcasts this out to the workers. We don't (currently) keep track of which worker has a job, nor do we even check the job queue to see if the message representing the job has been dequeued. Once upon a time, we did have the workers sort of spin on aborts until it actually got the job (assuming it didn't already have it) and then abort, but I argued that there has to be a better way.
So...I'm asking for help finding a better way. We do have some ideas; however, I figured others must have surely already solved this, so I'm checking for more elegant solutions. I'm currently leaning towards a queuebrowser + track worker that has job + target specific worker with abort request. It still seems like this might be overkill. I just need to guarantee that work can get aborted... If you have ideas or can point me to tutorial/samples/etc., it would be appreciated.
