Thank you! It is good to know the background of why some of these changes are happening.
Sent from my iPhone > On 2016/09/06, at 10:13, Gary Gregory <garydgreg...@gmail.com> wrote: > > Hi All, > > I am continuing some thread management clean ups. > > We use a couple of thread pools here and there and I plan on getting these to > shutdown consistently and predictably through the API I added a while back: > Configurator.shutdown(LoggerContext, long, TimeUnit). The idea is that when > you ask Log4j to shutdown, you can call this API and expect all threads to > stop terminate, no leaks. > > To do this right, I am going to implement AbstractLifeCycle stop() to call > stop(long, TimeUnit) with default values. This means that most classes that > implement stop() will now implement stop(long, TimeUnit) instead and can > choose to ignore these args in simple cases. > > Gary > > -- > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org > Java Persistence with Hibernate, Second Edition > JUnit in Action, Second Edition > Spring Batch in Action > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory
