This solves a bug where a task might be enqueued in the executor service
for longer than the stale timeout, so the cache believes that the
running task is in fact stale/canceled, and attempts to cancel it, but
this races against the task actually starting and trying to use the
files it expected to have access to.
To test this, the stale age and update interval can be sped up by setting these in MAVEN_OPTS:
-Dj2cl.diskcache.max_stale_age=1 -Dj2cl.diskcache.mark_active_update_delay_ms=500
This solves a bug where a task might be enqueued in the executor service for longer than the stale timeout, so the cache believes that the running task is in fact stale/canceled, and attempts to cancel it, but this races against the task actually starting and trying to use the files it expected to have access to.
Fixes #186