You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Martin Todorov (JIRA)" <ji...@apache.org> on 2013/04/04 17:21:16 UTC
[jira] [Comment Edited] (IVY-1197) OutOfMemoryError duriong
ivy:publish
[ https://issues.apache.org/jira/browse/IVY-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13622403#comment-13622403 ]
Martin Todorov edited comment on IVY-1197 at 4/4/13 3:20 PM:
-------------------------------------------------------------
Maarten,
Good news (sorry for the late reply): this indeed fixes the OOME! The artifact is uploaded within roughly 7 mins 30 secs.
Two things:
- If the credentials are incorrect, the file is still transferred before it fails. Perhaps this could be further polished up a bit, as it makes no sense to wait for it to fail late.
- Since the file is 1.7 GB, it is obviously rather large. Ivy spends a huge amount of time filling my console with unnecessary dots. I have filed IVY-1411 and linked it to this bug, simply because for smaller artifacts, most people wouldn't even care to complain about it as a bug. However, with an artifact of this size, I am sure it is bringing at least a minute and a half to two of unnecessary over head. (As you can see, with Maven it's achieving the same effect in around five and a half minutes). If the progress must be displayed, the I think it would be sufficient to have 10 or 20 dots as a representation of the entire progress and Ivy can calculate the percentage.
Could you please also look into these issues and give me an idea of when the next version of Ivy will be around?
Many thanks for your time,
Martin
was (Author: carlspring):
Maarten,
Good news (sorry for the late reply): this indeed fixes the OOME! The artifact is uploaded within roughly 7 mins 30 secs.
Two things:
- If the credentials are incorrect, the file is still transferred before it fails. Perhaps this could be further polished up a bit, as it makes no sense to wait for it to fail late.
- Since the file is 1.7 GB, it is obviously rather large. Ivy spends a huge amount of time filling my console with unnecessary dots. I have filed IVY-1411 and linked it to this bug, simply because for smaller artifacts, most people wouldn't even care to complain about it as a bug. However, with a artifact of this size, I am sure it is bringing at least a minute and a half to two of unnecessary over head. (As you can see, with Maven it's achieving the same effect in around five and a half minutes).
Could you please also look into these issues and give me an idea of when the next version of Ivy will be around?
Many thanks for your time,
Martin
> OutOfMemoryError duriong ivy:publish
> ------------------------------------
>
> Key: IVY-1197
> URL: https://issues.apache.org/jira/browse/IVY-1197
> Project: Ivy
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0
> Reporter: Michael Rumpf
> Attachments: ASF.LICENSE.NOT.GRANTED--clipboard.txt
>
>
> When publishing a large file, an OutOfMemoryError occurs.
> {code}
> [ivy:publish] published ppg to XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
> BUILD FAILED
> /export/build/hudson/jobs/ppg-rcp/workspace/ppg-rcp/com.daimler.ppg.rcp.builder/build-wrapper.xml:152: The following error occurred while executing this line:
> /export/build/hudson/jobs/ppg-rcp/workspace/ppg-rcp/com.daimler.ppg.rcp.builder/build-wrapper.xml:277: java.lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Arrays.java:2786)
> at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94)
> at sun.net.www.http.PosterOutputStream.write(PosterOutputStream.java:61)
> at org.apache.ivy.util.FileUtil.copy(FileUtil.java:168)
> at org.apache.ivy.util.url.BasicURLHandler.upload(BasicURLHandler.java:200)
> at org.apache.ivy.util.url.URLHandlerDispatcher.upload(URLHandlerDispatcher.java:82)
> at org.apache.ivy.util.FileUtil.copy(FileUtil.java:140)
> at org.apache.ivy.plugins.repository.url.URLRepository.put(URLRepository.java:85)
> at org.apache.ivy.plugins.repository.AbstractRepository.put(AbstractRepository.java:130)
> at org.apache.ivy.plugins.resolver.RepositoryResolver.put(RepositoryResolver.java:219)
> at org.apache.ivy.plugins.resolver.RepositoryResolver.publish(RepositoryResolver.java:209)
> at org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:282)
> at org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:261)
> at org.apache.ivy.core.publish.PublishEngine.publish(PublishEngine.java:170)
> at org.apache.ivy.Ivy.publish(Ivy.java:600)
> at org.apache.ivy.ant.IvyPublish.doExecute(IvyPublish.java:299)
> at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:277)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> at sun.reflect.GeneratedMethodAccessor101.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
> at org.apache.tools.ant.Task.perform(Task.java:348)
> at org.apache.tools.ant.Target.execute(Target.java:390)
> at org.apache.tools.ant.Target.performTasks(Target.java:411)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1397)
> at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1249)
> at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
> at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105)
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> Total time: 14 minutes 24 seconds
> Finished: FAILURE
> {code}
> The size of the file that is being uploaded is: 687712714, so around 650-700MB.
> The publish task is part of a Hudson Ant build where the artefacts are published to an Artifactory repository at the end.
> I have given the Job 1300MB for the max heap size.
> It seems as if the whole file is loaded into memory for the upload.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira