• Post Reply Bookmark Topic Watch Topic
  • New Topic

An unknown compilation problem occurred  RSS feed

 
Kevin Simonson
Ranch Hand
Posts: 223
2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I just got done replacing code:

with:

on the recommendation of some people on this forum. Now I execute "mvn clean install" and get the output:

INFO] Compiling 1412 source files to C:\Sandbox\ct\fsbe-domain\domain-prod\target\test-classes
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] An unknown compilation problem occurred
[INFO] 1 error
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] FT-FTBE-CT ........................................ SUCCESS [10.098s]
[INFO] FT-FTBE-CT fs-api ................................. SUCCESS [11.736s]
[INFO] FT-FTBE-CT fsbe-domain ............................ SUCCESS [3.862s]
[INFO] FT-FTBE-CT fsbe-domain domain-prod ................ FAILURE [7:49.975s]
[INFO] FT-FTBE-CT fsbe-domain fsbe-search-feeder ......... SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ............................ SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ct-config .................. SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ct-test-tools .............. SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ct-schema .................. SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ct-core .................... SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ct-webapp-common ........... SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ct-webapp .................. SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ct-webapp-development-login SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ct-functest-webapp ......... SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ct-functest-test-tools ..... SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ct-functest ................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8:16.188s
[INFO] Finished at: Fri Aug 29 16:40:54 MDT 2014
[INFO] Final Memory: 44M/442M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.0:testCompile (default-testCompile) on project fsbe-domain: Compilation failure
[ERROR] An unknown compilation problem occurred
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.0:testCompile (default-testCompile) on project fsbe-domain: Compilation failure
An unknown compilation problem occurred

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

Does anyone know what this means? "An unknown compilation problem occurred"? There's absolutely no information there at all.
 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 37465
539
Eclipse IDE Java VI Editor
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Can you re-run that build with the -X (Maven debug) flag? That should give more information about the error.
 
Kevin Simonson
Ranch Hand
Posts: 223
2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Jeanne Boyarsky wrote:Can you re-run that build with the -X (Maven debug) flag? That should give more information about the error.

I re-ran it with "mvn -e -X clean install" and I got:


[INFO] Compiling 1412 source files to C:\Sandbox\ct\fsbe-domain\domain-prod\targ
et\test-classes


The system is out of resources.
Consult the following stack trace for details.
java.lang.OutOfMemoryError: GC overhead limit exceeded
at com.sun.tools.javac.util.Convert.utf2string(Convert.java:143)
at com.sun.tools.javac.util.Name.toString(Name.java:146)
at java.lang.String.valueOf(String.java:2847)
at java.lang.StringBuilder.append(StringBuilder.java:128)
at com.sun.tools.javac.comp.Check.localClassName(Check.java:411)
at com.sun.tools.javac.comp.Enter.visitClassDef(Enter.java:371)
at com.sun.tools.javac.tree.JCTree$JCClassDecl.accept(JCTree.java:591)
at com.sun.tools.javac.comp.Enter.classEnter(Enter.java:258)
at com.sun.tools.javac.comp.Attr.visitClassDef(Attr.java:687)
at com.sun.tools.javac.tree.JCTree$JCClassDecl.accept(JCTree.java:591)
at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:431)
at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:418)
at com.sun.tools.javac.comp.Attr.attribStat(Attr.java:480)
at com.sun.tools.javac.comp.Attr.visitNewClass(Attr.java:1790)
at com.sun.tools.javac.tree.JCTree$JCNewClass.accept(JCTree.java:1372)
at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:431)
at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:418)
at com.sun.tools.javac.comp.Attr.attribArgs(Attr.java:504)
at com.sun.tools.javac.comp.Attr.visitApply(Attr.java:1513)
at com.sun.tools.javac.tree.JCTree$JCMethodInvocation.accept(JCTree.java
:1321)
at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:431)
at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:418)
at com.sun.tools.javac.comp.Attr.attribExpr(Attr.java:460)
at com.sun.tools.javac.comp.Attr.visitExec(Attr.java:1294)
at com.sun.tools.javac.tree.JCTree$JCExpressionStatement.accept(JCTree.j
ava:1167)
at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:431)
at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:418)
at com.sun.tools.javac.comp.Attr.attribStat(Attr.java:480)
at com.sun.tools.javac.comp.Attr.attribStats(Attr.java:496)
at com.sun.tools.javac.comp.Attr.visitBlock(Attr.java:918)
at com.sun.tools.javac.tree.JCTree$JCBlock.accept(JCTree.java:781)
at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:431)
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] An unknown compilation problem occurred
[INFO] 1 error
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] FT-FTBE-CT ........................................ SUCCESS [14.072s]
[INFO] FT-FTBE-CT fs-api ................................. SUCCESS [14.586s]
[INFO] FT-FTBE-CT fsbe-domain ............................ SUCCESS [4.087s]
[INFO] FT-FTBE-CT fsbe-domain domain-prod ................ FAILURE [8:05.117s]
[INFO] FT-FTBE-CT fsbe-domain fsbe-search-feeder ......... SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ............................ SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ct-config .................. SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ct-test-tools .............. SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ct-schema .................. SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ct-core .................... SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ct-webapp-common ........... SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ct-webapp .................. SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ct-webapp-development-login SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ct-functest-webapp ......... SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ct-functest-test-tools ..... SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ct-functest ................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8:38.392s
[INFO] Finished at: Sat Aug 30 15:58:22 MDT 2014
[INFO] Final Memory: 45M/436M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.
0:testCompile (default-testCompile) on project fsbe-domain: Compilation failure
[ERROR] An unknown compilation problem occurred
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal o
rg.apache.maven.plugins:maven-compiler-plugin:3.0:testCompile (default-testCompi
le) on project fsbe-domain: Compilation failure
An unknown compilation problem occurred

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:145)


Is this an indication that I have a memory leak? How can that be, when every other software engineer where I work runs "mvn clean install" without any problem at all?
 
Kevin Simonson
Ranch Hand
Posts: 223
2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Kevin Simonson wrote:
Jeanne Boyarsky wrote:Can you re-run that build with the -X (Maven debug) flag? That should give more information about the error.

I re-ran it with "mvn -e -X clean install" and I got:


[INFO] Compiling 1412 source files to C:\Sandbox\ct\fsbe-domain\domain-prod\targ
et\test-classes


The system is out of resources.
Consult the following stack trace for details.
java.lang.OutOfMemoryError: GC overhead limit exceeded
at com.sun.tools.javac.util.Convert.utf2string(Convert.java:143)
at com.sun.tools.javac.util.Name.toString(Name.java:146)
at java.lang.String.valueOf(String.java:2847)
at java.lang.StringBuilder.append(StringBuilder.java:128)
at com.sun.tools.javac.comp.Check.localClassName(Check.java:411)
at com.sun.tools.javac.comp.Enter.visitClassDef(Enter.java:371)
at com.sun.tools.javac.tree.JCTree$JCClassDecl.accept(JCTree.java:591)
at com.sun.tools.javac.comp.Enter.classEnter(Enter.java:258)
at com.sun.tools.javac.comp.Attr.visitClassDef(Attr.java:687)
at com.sun.tools.javac.tree.JCTree$JCClassDecl.accept(JCTree.java:591)
at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:431)
at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:418)
at com.sun.tools.javac.comp.Attr.attribStat(Attr.java:480)
at com.sun.tools.javac.comp.Attr.visitNewClass(Attr.java:1790)
at com.sun.tools.javac.tree.JCTree$JCNewClass.accept(JCTree.java:1372)
at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:431)
at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:418)
at com.sun.tools.javac.comp.Attr.attribArgs(Attr.java:504)
at com.sun.tools.javac.comp.Attr.visitApply(Attr.java:1513)
at com.sun.tools.javac.tree.JCTree$JCMethodInvocation.accept(JCTree.java
:1321)
at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:431)
at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:418)
at com.sun.tools.javac.comp.Attr.attribExpr(Attr.java:460)
at com.sun.tools.javac.comp.Attr.visitExec(Attr.java:1294)
at com.sun.tools.javac.tree.JCTree$JCExpressionStatement.accept(JCTree.j
ava:1167)
at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:431)
at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:418)
at com.sun.tools.javac.comp.Attr.attribStat(Attr.java:480)
at com.sun.tools.javac.comp.Attr.attribStats(Attr.java:496)
at com.sun.tools.javac.comp.Attr.visitBlock(Attr.java:918)
at com.sun.tools.javac.tree.JCTree$JCBlock.accept(JCTree.java:781)
at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:431)
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] An unknown compilation problem occurred
[INFO] 1 error
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] FT-FTBE-CT ........................................ SUCCESS [14.072s]
[INFO] FT-FTBE-CT fs-api ................................. SUCCESS [14.586s]
[INFO] FT-FTBE-CT fsbe-domain ............................ SUCCESS [4.087s]
[INFO] FT-FTBE-CT fsbe-domain domain-prod ................ FAILURE [8:05.117s]
[INFO] FT-FTBE-CT fsbe-domain fsbe-search-feeder ......... SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ............................ SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ct-config .................. SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ct-test-tools .............. SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ct-schema .................. SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ct-core .................... SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ct-webapp-common ........... SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ct-webapp .................. SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ct-webapp-development-login SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ct-functest-webapp ......... SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ct-functest-test-tools ..... SKIPPED
[INFO] FT-FTBE-CT ct-rest-api ct-functest ................ SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8:38.392s
[INFO] Finished at: Sat Aug 30 15:58:22 MDT 2014
[INFO] Final Memory: 45M/436M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.
0:testCompile (default-testCompile) on project fsbe-domain: Compilation failure
[ERROR] An unknown compilation problem occurred
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal o
rg.apache.maven.plugins:maven-compiler-plugin:3.0:testCompile (default-testCompi
le) on project fsbe-domain: Compilation failure
An unknown compilation problem occurred

at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:145)


Is this an indication that I have a memory leak? How can that be, when every other software engineer where I work runs "mvn clean install" without any problem at all?

Nobody responded to this over the Labor Day weekend, so I thought I'd repost it. I've got this project on Maven. The original "pom.xml" file had these settings:

I've upped it to:

And I'm still getting the message, "The system is out of resources. / Consult the following stack trace for details. / java.lang.OutOfMemoryError: GC overhead limit exceeded"

The mentioned stack trace begins with:

at java.lang.String.toCharArray(String.java:2746)
at com.sun.tools.javac.util.Name$Table.fromString(Name.java:203)
at com.sun.tools.javac.util.Names.fromString(Names.java:288)
at com.sun.tools.javac.comp.Lower.accessName(Lower.java:876)
at com.sun.tools.javac.comp.Lower.accessSymbol(Lower.java:960)
at com.sun.tools.javac.comp.Lower.access(Lower.java:1126)
at com.sun.tools.javac.comp.Lower.visitIdent(Lower.java:3135)
at com.sun.tools.javac.tree.JCTree$JCIdent.accept(JCTree.java:1705)
at com.sun.tools.javac.tree.TreeTranslator.translate(TreeTranslator.java:58)

This is so completely bizarre. My co-worker has the exact same code, except that I fixed the problem the compiler was having with the references to BASE64Encoder, and except for the <maxPermSize> and <maxMemory> settings. My settings are 16 times as large as his settings, and yet when he runs the tests they succeed, while when I run the exact same tests I get an OutOfMemoryError. Does anybody have any idea why this might be happening?
 
Jayesh A Lalwani
Rancher
Posts: 2762
32
Eclipse IDE Spring Tomcat Server
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You increased the memory for surefire. SUrefire is used to run unit tests. THe problem is you need more memory during compilation. TO increase the memory given to the compiler, you need to give more memory to maven itself by changing the the MAVEN_OPTS environment variable. Try setting MAVEN_OPTS to -Xmx1024m
 
Kevin Simonson
Ranch Hand
Posts: 223
2
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Jayesh A Lalwani wrote:You increased the memory for surefire. SUrefire is used to run unit tests. THe problem is you need more memory during compilation. TO increase the memory given to the compiler, you need to give more memory to maven itself by changing the the MAVEN_OPTS environment variable. Try setting MAVEN_OPTS to -Xmx1024m

Thanks Jayesh! That solved the problem; I was able to get a successful build.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!