Netflix/curator — Issue #17: Shutdown problems with ConnectionStateManager
Author: ntolia
Created: 2012-01-13 21:59:35+00:00
State: open

Yes, I know I should be cleanly shutting down any ```CuratorFramework``` instances but I noticed that, if I failed to do so, my JVM would never terminate. This occurs even if I pass a daemon thread factory to ```CuratorFrameworkFactory.Builder```. On looking through the code, I see that ```ConnectionStateManager``` builds its own thread factor instead of using what was provided to the builder. Is this intentional?