System Takes 30 min to build a module, most of the time takes to resolve the dependencies

Old Forum
1

System Takes 30 min to build a module, most of the time takes to resolve the dependencies.Is there any way to speed up the resolving the dependencies.

some time build will fail with the below mention exception

The system is out of resources. Consult the following stack trace for details. java.lang.OutOfMemoryError: Java heap space

at java.util.Arrays.copyOfRange(Arrays.java:3658)

at java.lang.String.(String.java:201)

at java.lang.String.toLowerCase(String.java:2632)

at java.io.WinNTFileSystem.hashCode(WinNTFileSystem.java:640)

at java.io.File.hashCode(File.java:2132)

at com.sun.tools.javac.file.RegularFileObject.hashCode(RegularFileObject.java:240)

at java.util.HashMap.hash(HashMap.java:338)

at java.util.HashMap.get(HashMap.java:556)

at com.sun.tools.javac.util.AbstractLog.getSource(AbstractLog.java:64)

at com.sun.tools.javac.util.AbstractLog.useSource(AbstractLog.java:57)

at com.sun.tools.javac.file.RegularFileObject.getCharContent(RegularFileObject.java:115)

at com.sun.tools.javac.file.RegularFileObject.getCharContent(RegularFileObject.java:53)

at com.sun.tools.javac.util.DiagnosticSource.initBuf(DiagnosticSource.java:185)

at com.sun.tools.javac.util.DiagnosticSource.findLine(DiagnosticSource.java:153)

at com.sun.tools.javac.util.DiagnosticSource.getLineNumber(DiagnosticSource.java:77)

at com.sun.tools.javac.util.JCDiagnostic.(JCDiagnostic.java:399)

at com.sun.tools.javac.util.JCDiagnostic$Factory.create(JCDiagnostic.java:238)

at com.sun.tools.javac.util.JCDiagnostic$Factory.create(JCDiagnostic.java:223)

at com.sun.tools.javac.comp.Resolve$AbstractMethodCheck.reportMC(Resolve.java:772)

at com.sun.tools.javac.comp.Resolve$4$2.report(Resolve.java:864)

at com.sun.tools.javac.comp.Check.checkType(Check.java:546)

at com.sun.tools.javac.comp.Attr$ResultInfo.check(Attr.java:510)

at com.sun.tools.javac.comp.Resolve$MethodResultInfo.check(Resolve.java:978)

at com.sun.tools.javac.comp.Resolve$4.checkArg(Resolve.java:822)

at com.sun.tools.javac.comp.Resolve$AbstractMethodCheck.argumentsAcceptable(Resolve.java:733)

at com.sun.tools.javac.comp.Resolve$4.argumentsAcceptable(Resolve.java:831)

at com.sun.tools.javac.comp.Resolve.rawInstantiate(Resolve.java:578)

at com.sun.tools.javac.comp.Resolve.selectBest(Resolve.java:1418)

at com.sun.tools.javac.comp.Resolve.findMethodInScope(Resolve.java:1597)

at com.sun.tools.javac.comp.Resolve.findMethod(Resolve.java:1668)

at com.sun.tools.javac.comp.Resolve.findMethod(Resolve.java:1641)

at com.sun.tools.javac.comp.Resolve.findFun(Resolve.java:1804) :ascCommon:compileJava FAILED

My System Configuration RAM:4GB Processor Speed:2.66GHz Windows7 32 Bit

2

Can you please provide the output of ‘gradle -v’, wrapped in HTML code tags.

3

Hi Peter Niederwieser ,

Please find the below mentioned details as suggested.

C:\StrykerToolNiagara4\NIAGARA4_TECH_STUDY\ASCCommon\SourceCode\ascCommon>gradle -v

------------------------------------------------------------ Gradle 1.10 ------------------------------------------------------------

Build time:

2013-12-17 09:28:15 UTC Build number: none Revision:

36ced393628875ff15575fa03d16c1349ffe8bb6

Groovy:

1.8.6 Ant:

Apache Ant™ version 1.9.2 compiled on July 8 2013 Ivy:

2.2.0 JVM:

1.8.0 (Oracle Corporation 25.0-b70) OS:

Windows 7 6.1 x86

C:\StrykerToolNiagara4\NIAGARA4_TECH_STUDY\ASCCommon\SourceCode\ascCommon>

4

We’d be just guessing here. Since Gradle is an application running using JVM you can take a look at JDK troubleshooting guide (http://docs.oracle.com/javase/7/docs/webnotes/tsg/). In general I’d recommend you to make sure that Gradle processes have enough memory to perform their job (your compilation is now running out of memory so the Java heap space can be too small). At the same time check that it is not too much memory to cause swaping to a disk file as this will seriously hurt the performance.