[jira] [Commented] (IVY-1197) OutOfMemoryError during ivy:publish

2018-08-02 Thread jaikiran pai (JIRA)


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

jaikiran pai commented on IVY-1197:
---

Charles, this should work fine with 2.5.0-rc1 where we use 4.x of Apache HTTP 
client library. You will have to include that in your classpath so that Ivy 
picks that up instead of the JDK implementation.


> OutOfMemoryError during 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
>Priority: Major
> Attachments: ASF.LICENSE.NOT.GRANTED--clipboard.txt, ivylarge.zip, 
> org.apache.ivy.util.url.HttpClientHandler.patch
>
>
> When publishing a large file, an OutOfMemoryError occurs.
> {code}
> [ivy:publish] published ppg to 
> 
> 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 was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (IVY-1197) OutOfMemoryError during ivy:publish

2018-08-02 Thread Charles Breingan (JIRA)


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

Charles Breingan commented on IVY-1197:
---

Is this still an issue? Has JDK or Apache resolved this yet? 

> OutOfMemoryError during 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
>Priority: Major
> Attachments: ASF.LICENSE.NOT.GRANTED--clipboard.txt, ivylarge.zip, 
> org.apache.ivy.util.url.HttpClientHandler.patch
>
>
> When publishing a large file, an OutOfMemoryError occurs.
> {code}
> [ivy:publish] published ppg to 
> 
> 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 was sent by Atlassian JIRA
(v7.6.3#76005)


[Bug 62594] junitreport saxon frames fails on windows

2018-08-02 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62594

--- Comment #4 from mcwar...@gmail.com ---
Java vendor is Oracle.

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

[Bug 62594] junitreport saxon frames fails on windows

2018-08-02 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62594

mcwar...@gmail.com changed:

   What|Removed |Added

 OS||All

--- Comment #3 from mcwar...@gmail.com ---
$ java -version
java version "1.8.0_131"
Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)

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

[Bug 62594] junitreport saxon frames fails on windows

2018-08-02 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62594

--- Comment #2 from Jaikiran Pai  ---
Could you tell us which vendor and version of Java runtime is this? The output
of:

java -version

will help. I'm mostly curious since a similar issue has been reported in a
different context in Windows and we haven't been able to narrow it down.

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

[Bug 62594] junitreport saxon frames fails on windows

2018-08-02 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62594

mcwar...@gmail.com changed:

   What|Removed |Added

 OS|All |Windows 10

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

[Bug 62594] junitreport saxon frames fails on windows

2018-08-02 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62594

--- Comment #1 from mcwar...@gmail.com ---
Created attachment 36067
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=36067&action=edit
Fix-junit-frames-saxon.xsl-to-work-on-windows.patch

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

[Bug 62594] junitreport saxon frames fails on windows

2018-08-02 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62594

mcwar...@gmail.com changed:

   What|Removed |Added

 OS||All
Summary|junitreport saxon fails on  |junitreport saxon frames
   |windows |fails on windows

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

[Bug 62594] New: junitreport saxon fails on windows

2018-08-02 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=62594

Bug ID: 62594
   Summary: junitreport saxon fails on windows
   Product: Ant
   Version: 1.10.5
  Hardware: PC
Status: NEW
  Severity: normal
  Priority: P2
 Component: Optional Tasks
  Assignee: notifications@ant.apache.org
  Reporter: mcwar...@gmail.com
  Target Milestone: ---

Created attachment 36066
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=36066&action=edit
sample-build.xml

When running junitreport frames using junitreport-saxon.xsl on windows the
following exception occurs:

Caused by: java.net.MalformedURLException: unknown protocol: c

Upon further investigation it's because the the xsl:result-document needs to be
a URI I believe "..xsl:result-document href="file:///{$output.dir}.."

I've attached sample build.xml that replicates the issue.

Full stack trace:

BUILD FAILED
C:\repo\code\other\junitreport-xsl-saxon-windows\build.xml:26: Errors while
applying transformations: Fatal error during transformation using
jar:file:/C:/tools/apache-ant-1.10.5/lib/ant-junit.jar!/org/apache/tools/ant/taskdefs/optional/junit/xsl/junit-frames-saxon.xsl:
Resolved URL is malformed; SystemID:
jar:file:/C:/tools/apache-ant-1.10.5/lib/ant-junit.jar!/org/apache/tools/ant/taskdefs/optional/junit/xsl/junit-frames-saxon.xsl;
Line#: 39; Column#: 62
at
org.apache.tools.ant.taskdefs.optional.TraXLiaison.fatalError(TraXLiaison.java:544)
at
net.sf.saxon.lib.DelegatingErrorListener.fatalError(DelegatingErrorListener.java:46)
at net.sf.saxon.Controller.reportFatalError(Controller.java:958)
at net.sf.saxon.Controller.transform(Controller.java:1914)
at
net.sf.saxon.s9api.XsltTransformer.transform(XsltTransformer.java:588)
at
net.sf.saxon.jaxp.TransformerImpl.transform(TransformerImpl.java:185)
at
org.apache.tools.ant.taskdefs.optional.TraXLiaison.transform(TraXLiaison.java:204)
at
org.apache.tools.ant.taskdefs.XSLTProcess.process(XSLTProcess.java:870)
at
org.apache.tools.ant.taskdefs.XSLTProcess.execute(XSLTProcess.java:408)
at
org.apache.tools.ant.taskdefs.optional.junit.AggregateTransformer.transform(AggregateTransformer.java:281)
at
org.apache.tools.ant.taskdefs.optional.junit.XMLResultAggregator.execute(XMLResultAggregator.java:157)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:99)
at org.apache.tools.ant.Task.perform(Task.java:350)
at org.apache.tools.ant.Target.execute(Target.java:449)
at org.apache.tools.ant.Target.performTasks(Target.java:470)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1388)
at org.apache.tools.ant.Project.executeTarget(Project.java:1361)
at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.Main.runBuild(Main.java:834)
at org.apache.tools.ant.Main.startAnt(Main.java:223)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:284)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:101)
Caused by: net.sf.saxon.trans.XPathException: Resolved URL is malformed
at
net.sf.saxon.lib.StandardOutputResolver.resolve(StandardOutputResolver.java:98)
at
net.sf.saxon.expr.instruct.ResultDocument.getResult(ResultDocument.java:523)
at
net.sf.saxon.expr.instruct.ResultDocument.processInstruction(ResultDocument.java:448)
at
net.sf.saxon.Configuration.processResultDocument(Configuration.java:2136)
at
net.sf.saxon.expr.instruct.ResultDocument.process(ResultDocument.java:382)
at
net.sf.saxon.expr.instruct.ResultDocument.processLeavingTail(ResultDocument.java:368)
at net.sf.saxon.expr.instruct.Block.processLeavingTail(Block.java:653)
at
net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(TemplateRule.java:353)
at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:456)
at
net.sf.saxon.trans.TextOnlyCopyRuleSet.process(TextOnlyCopyRuleSet.java:65)
at net.sf.saxon.trans.Mode.applyTemplates(Mode.java:433)
at net.sf.saxon.Controller.transformDocument(Controller.java:2321)
at net.sf.saxon.Controller.transform(Controller.java:1892)
... 24 more
Caused by: java.net.MalformedURLException: unknown protocol: c
at java.net.URL.(URL.java:600)
at java.net.URL.(URL.java:490)
at java.net.URL.(UR

[jira] [Commented] (IVY-1104) ivy.deps.changed does not work with extra attributes

2018-08-02 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on IVY-1104:
-

Github user twogee commented on the issue:

https://github.com/apache/ant-ivy/pull/73
  
No dispute here; however, that may need some adjustment to XSL, which 
transforms XML report to HTML.


> ivy.deps.changed does not work with extra attributes
> 
>
> Key: IVY-1104
> URL: https://issues.apache.org/jira/browse/IVY-1104
> Project: Ivy
>  Issue Type: Bug
>Reporter: Juha Ranta
>Priority: Major
>
> If you have extra attributes in module B and then do resolve in module A 
> which depends on B, the property ivy.deps.changed is always set to true. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (IVY-1104) ivy.deps.changed does not work with extra attributes

2018-08-02 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on IVY-1104:
-

Github user aprelev commented on the issue:

https://github.com/apache/ant-ivy/pull/73
  
To be honest, I do not like the idea of imposing implicit requirements on 
naming of namespaces. Escaping dashes in prefixes seems more robust and 
error-prone given correct codec is implemented. I will look into that and 
update this PR accordingly.


> ivy.deps.changed does not work with extra attributes
> 
>
> Key: IVY-1104
> URL: https://issues.apache.org/jira/browse/IVY-1104
> Project: Ivy
>  Issue Type: Bug
>Reporter: Juha Ranta
>Priority: Major
>
> If you have extra attributes in module B and then do resolve in module A 
> which depends on B, the property ivy.deps.changed is always set to true. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (IVY-1104) ivy.deps.changed does not work with extra attributes

2018-08-02 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on IVY-1104:
-

Github user twogee commented on the issue:

https://github.com/apache/ant-ivy/pull/73
  
Besides, `extra-` has to be kept for backwards compatibility.


> ivy.deps.changed does not work with extra attributes
> 
>
> Key: IVY-1104
> URL: https://issues.apache.org/jira/browse/IVY-1104
> Project: Ivy
>  Issue Type: Bug
>Reporter: Juha Ranta
>Priority: Major
>
> If you have extra attributes in module B and then do resolve in module A 
> which depends on B, the property ivy.deps.changed is always set to true. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (IVY-1104) ivy.deps.changed does not work with extra attributes

2018-08-02 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on IVY-1104:
-

Github user twogee commented on the issue:

https://github.com/apache/ant-ivy/pull/73
  
`'-'` cannot be escaped since the spec does not permit `&#` in names 
(please have a look at the link in my previous comment). If escaping `'-'` in 
namespace prefixes works better than using fancy separators, fine. I was 
actually thinking about using some exotic glyphs (the spec seems to permit 
`'·'` aka middot in XML names; so perhaps a tripple middot as a separator? 
Would look pretty in a browser, no need to fiddle with XSL that helps to 
display reports).

`extra-` allows to find the attributes from other namespaces easily, 
AFAICS. Unfortunately (or fortunately?) middot cannot be used as the first 
character in an XML name.


> ivy.deps.changed does not work with extra attributes
> 
>
> Key: IVY-1104
> URL: https://issues.apache.org/jira/browse/IVY-1104
> Project: Ivy
>  Issue Type: Bug
>Reporter: Juha Ranta
>Priority: Major
>
> If you have extra attributes in module B and then do resolve in module A 
> which depends on B, the property ivy.deps.changed is always set to true. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (IVY-1104) ivy.deps.changed does not work with extra attributes

2018-08-02 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on IVY-1104:
-

Github user aprelev commented on the issue:

https://github.com/apache/ant-ivy/pull/73
  
> Using a simple '-' as a separator may cause trouble if somebody decides 
to use a namespace prefix with '-'.

I don't actually see a problem with that: we can
- either escape dashes with some other character, like `.` (`-ns-:-foo.` → 
`extra-.-ns.--.-foo..`),
- or replace them with `-` (`-ns-:-foo.` → 
`extra--ns---foo.`).


> ivy.deps.changed does not work with extra attributes
> 
>
> Key: IVY-1104
> URL: https://issues.apache.org/jira/browse/IVY-1104
> Project: Ivy
>  Issue Type: Bug
>Reporter: Juha Ranta
>Priority: Major
>
> If you have extra attributes in module B and then do resolve in module A 
> which depends on B, the property ivy.deps.changed is always set to true. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)