ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 46338] New: Starting forked java process cause a lot of blocking threads in Ant
Date Thu, 04 Dec 2008 14:24:57 GMT

           Summary: Starting forked java process cause a lot of blocking
                    threads in Ant
           Product: Ant
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: critical
          Priority: P2
         Component: Core tasks

Created an attachment (id=22989)
 --> (
Test Java class

We are running into some problems after running a lot of integration tests in
our build. After a lot of trail & error we ran into a situation with Ant. We
suspect that this might cause our problems.

We created a simple test (see attachemts) to reproduce this problem.
How to test:
1. Compile the class
2. Run the ant script
3. Connect to the ant process using JConsole

What are the results?

1. For each antcall to the target Blah a java process is forked.
2. In JConsole we see at that moment that a couple of java threads are created
(3 or 4)
3. When the forked process is finished, the threads created disappear. Well,
all disappear but one! For each forked process a thread remains in a blocked

So after many antcalls starting these forked processes the number of blocking
threads starts to get out of hands.

I would expect all threads associated in the ant process with the forked java
process would be cleaned up after the forked process is done. It appears this
is not the case.

As we suspect this being the cause of some of our nightly builds that just seem
to hang after a while, we hope somebody has ideas on how to approach this

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

View raw message