Return-Path: 
 <notifications-return-19061-apmail-ant-notifications-archive=ant.apache.org@ant.apache.org>
X-Original-To: apmail-ant-notifications-archive@minotaur.apache.org
Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id A93F2CE28
	for <apmail-ant-notifications-archive@minotaur.apache.org>;
 Thu, 10 May 2012 13:34:12 +0000 (UTC)
Received: (qmail 20984 invoked by uid 500); 10 May 2012 13:34:12 -0000
Delivered-To: apmail-ant-notifications-archive@ant.apache.org
Received: (qmail 20953 invoked by uid 500); 10 May 2012 13:34:12 -0000
Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:notifications-help@ant.apache.org>
List-Unsubscribe: <mailto:notifications-unsubscribe@ant.apache.org>
List-Post: <mailto:notifications@ant.apache.org>
List-Id: <notifications.ant.apache.org>
Reply-To: dev@ant.apache.org
Delivered-To: mailing list notifications@ant.apache.org
Received: (qmail 20945 invoked by uid 99); 10 May 2012 13:34:12 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 May 2012 13:34:12 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 May 2012 13:34:10 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id 444761466E
	for <notifications@ant.apache.org>; Thu, 10 May 2012 13:33:49 +0000 (UTC)
Date: Thu, 10 May 2012 13:33:49 +0000 (UTC)
From: "Daniel Holmes (JIRA)" <jira@apache.org>
To: notifications@ant.apache.org
Message-ID: 
 <2125041251.49213.1336656829294.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1542178774.12642.1300479509497.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (IVY-1277) "Too many open files" error during
 ivy:buildlist
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/IVY-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13272317#comment-13272317 ] 

Daniel Holmes commented on IVY-1277:
------------------------------------

I did just encounter this for the first time.  Happened as I was experimenting with URL resolver rather than a basic file resolver which we had been using for nearly 2 years.  Does seem intermittent because my second build seemed to proceed fine.
                
> "Too many open files" error during ivy:buildlist
> ------------------------------------------------
>
>                 Key: IVY-1277
>                 URL: https://issues.apache.org/jira/browse/IVY-1277
>             Project: Ivy
>          Issue Type: Bug
>    Affects Versions: 2.2.0
>         Environment: 64bit Ubuntu, ant 1.7.1
>            Reporter: Garrett Kiel
>            Priority: Minor
>
> impossible to parse ivy file for /home/blah/blah/blah/build/build.xml: ivyfile=/home/blah/blah/blah/build/ivy.xml exception=java.text.ParseException: /home/blah/blah/blah/build/ivy.xml (Too many open files) in file:/home/blah/blah/blah/build/ivy.xml
> This error has intermittently happened to a number of people I work with during a particular buildlist call that looks like this:
> {code:xml}
> <ivy:buildlist reference="@{module}.depends" root="@{module}" excluderoot="true" onlydirectdep="true">
>     <fileset dir="${core.home}" includes="*/build/build.xml" excludes="build/"/>
> </ivy:buildlist>
> {code}
> (It's nested in a <for> loop that iterates over every @{module} in our project)
> We have approximately 50-60 ivy modules in our project just for reference.  Additionally, this error only started coming up when we upgraded to 2.2.0 from 2.0.0-beta2.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira