https://issues.apache.org/bugzilla/show_bug.cgi?id=50486
--- Comment #54 from Patric Rufflar <[email protected]> --- >If a thread doesn't clean up behind itself it leaves it up for someone else to >>do the dirty work - not nice. I totally agree - that's way it should be. Unfortunately this seems not clear for everybody and there will always be enough code around (e.g. 3rd party libraries) which violates this principle (just look at this bug - it took a long time to get log4j cleaning up the resources it acquired) >What you propose is IMO nothing but a fallback for applications that don't >adhere to that simple pattern. Yes, that's true. But a failsafe which prevents a crash of a production server is better than insisting a perfect world. And a shutdown procedure that has some effect on other threads is not uncommon - almost any shutdown() I am aware of concerns the outer world/other threads aswell (if you think of connection pools, application servers, operating systems...). -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
