Minor Description
It seems like ScheduledThreadPoolExecutor's remove() function sometimes does not remove the runnable specified. This does not cause any functionality problems, just spills lot of stuff into logs during reconfiguration, and can cause runnables to be executed unnecessarily, even though they return immediately.