I post hundreds of http request task with block() to scheduler. Sometimes I need to close my application and dispose the scheduler, then it'll throw interruptedException when each task get http response and notice the scheduler is disposed.

I'm wondering why not use shutdown() instead of shutdownNow() in dispose()?

Motivation

Currently when BoundedElasticScheduler call dispose(), it will halt all waiting tasks. Let waiting task finish not halt them toughly.

Desired solution

Use shutdown() instead of shutdownNow() in dispose().