Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!us.feeder.erje.net!news2.arglkargh.de!nuzba.szn.dk!pnx.dk!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Robert Klemme Newsgroups: comp.lang.java.programmer Subject: Re: Threads, waiting for last one to finish Date: Sat, 26 Jan 2013 17:20:59 +0100 Lines: 21 Message-ID: References: <50f264aa$0$80119$742ec2ed@news.sonic.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net DzgQ6qfCSWRu9C+w+iCe8AZSbOL1cysgbCTut4J6K59aIsfSAuJGzS1Wung3I/eIM= Cancel-Lock: sha1:AGG6/kUEarUAYtTEb3ANZoHTIU4= User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 In-Reply-To: Xref: csiph.com comp.lang.java.programmer:21739 On 25.01.2013 20:46, Wanja Gayk wrote: > In article <50f264aa$0$80119$742ec2ed@news.sonic.net>, Kevin McMurtrie > (mcmurtrie@pixelmemory.us) says... > >> The Executor classes are horribly buggy. Pool size adjustment, idle >> timeouts, and shutdown sequences do NOT work. Some of the features are >> impossible to implement efficiently so Sun instead chose to implement >> them incorrectly. > > Could be more specific? See his reply from January 16. in this thread. :-) Kind regards robert -- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/