[
https://issues.apache.org/jira/browse/MASSEMBLY-774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14593010#comment-14593010
]
Kristian Rosenvold edited comment on MASSEMBLY-774 at 6/19/15 5:01 AM:
-----------------------------------------------------------------------
Can you run with mvn -e and include the stacktrace of where the file allocation
is failing ?
(This was fixed in https://github.com/codehaus-plexus/plexus-archiver/issues/6,
but there apperas to be multiple code paths with this problem then..)
was (Author: krosenvold):
Can you run with mvn -e and include the stacktrace of where the file allocation
is failing ?
> too many open files
> -------------------
>
> Key: MASSEMBLY-774
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-774
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.5.5
> Reporter: Dan Armbrust
>
> I ran across this -
> http://mail-archives.apache.org/mod_mbox/maven-dev/201501.mbox/%[email protected]%3E
> - and since I'm making huge zip files, I thought I would give it a try.
> I configured as:
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-assembly-plugin</artifactId>
> <version>2.5.5</version>
> <dependencies>
> <dependency>
> <groupId>org.codehaus.plexus</groupId>
> <artifactId>plexus-archiver</artifactId>
> <version>3.0.1</version>
> </dependency>
> <dependency>
> <groupId>org.codehaus.plexus</groupId>
> <artifactId>plexus-io</artifactId>
> <version>2.6</version>
> </dependency>
> </dependencies>
> </plugin>
> But this lead to a failure:
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.5.5:single (zip) on project
> ... sememe/seg.3182.sememe.map (Too many open files) -> [Help 1]
> I certainly could raise my ulimit:
> darmbrust@overkill:/mnt/STORAGE/Work/Apelon/Workspaces/ISAAC-Core-2/va-solor-goods$
> ulimit -a
> ...
> open files (-n) 1024
> But it seems it would be better if the zip process limited itself to a
> reasonable number of open files. I don't know the algorithm... but it seems
> that double or triple the processor count would be more than enough.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
