disconnect before calling scheduler methods, and detect queue changes properly by getting the correct current queue
submission handler now stores the fact that it is running a sub in redis, so that the server can avoid requeuing that sub, avoiding possibility of two handlers handling the same sub at the same time
added comment about race condition between checking if a sub was grabbed and adding it to the redis queue
do not reselect_from_db for every beat_heart
avoid db access during most loops of the submission handler
check that starting the redis server worked and complain if not
run() now accepts a redis object to do a lock in preference to the db lock; Submission claim_and_run() passes the redis object on
pipelinesetup->trigger() now takes a redis object to lock the des; submission handler passes on the redis to trigger()