ist
Subject: RE: OutOfMemoryError: unable to create new native thread
Inclusion of revisions 579975 and 711860 did not resolve the eternal
threads issue. I'll try the inputstring work around on all the forked
tasks.
Thanks, Mike
-Original Message-
From: Stefan Bodewig [mailto:bode.
user@ant.apache.org
Subject: Re: OutOfMemoryError: unable to create new native thread
On 2009-01-30, Murray, Mike wrote:
> All the "hung" threads display the same "blocked" scenario as
> thread-1199.
> Name: Thread-1199
> State: BLOCKED on java.io.bufferedinputstr...@1
On 2009-01-30, Murray, Mike wrote:
> All the "hung" threads display the same "blocked" scenario as
> thread-1199.
> Name: Thread-1199
> State: BLOCKED on java.io.bufferedinputstr...@1b5973f owned by:
> Thread-11
> Total blocked: 1 Total waited: 0
> Stack trace:
> java.io.BufferedInputStream.
}
From: Murray, Mike
Sent: Thursday, January 29, 2009 9:17 PM
To: 'Ant Users List'
Subject: OutOfMemoryError: unable to create new native thread
Since I'm allocating the JVM 1G for Heap and 370M for PermGen, the OS
runs out of room for all the threads.
I don't
Since I'm allocating the JVM 1G for Heap and 370M for PermGen, the OS
runs out of room for all the threads.
I don't know why the threads continually climb while the builds runs.
By the time it dies, the jconsole shows 888 lives threads, 890 peak and
4,013 total. It seems some of the parallel
