I just a comment about GC. Libraries that call for GCs are not very application friendly. When a library that is a small part of an application explicitly invokes GCs, it can have a dramatic effect on the performance of the whole application. This must have been seen as a common problem, because Java 1.4 offers the -XX:+DisableExplicitGC option to disable the System.gc() and return control of GC back to the JVM where it belongs.
Dennis Cook BeVocal, Inc. tel: 650-641-1424 fax: 650-210-9275 -----Original Message----- From: Ortwin Glück [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 12, 2003 12:21 AM To: Commons HttpClient Project Subject: Re: DO NOT REPLY [Bug 24309] - MultiThreadedHttpConnectionManager daemon Thread never GC'd Mike, in the test case I would rather introduce a Thread.sleep AFTER the System.gc() call as well to give the GC time to run. GC happens asynchronously. The System.gc() call is not blocking! Odi > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24309 > > ------- Additional Comments From [EMAIL PROTECTED] 2003-11-12 00:27 ------- > Any more thoughts on this one, or should I apply? > > Mike > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
