Does setting higher heap memories in jvm flags(i.e. -Xmx) help?
On Mon, May 23, 2011 at 4:23 PM, bogl wrote:
> Hello
> I'm trying to create generated-sources and generated-test-sources
> files for protobuf-2.4.1 (java), but getting an error message:
>
> [INFO]
>
> [ERROR] BUILD FAILURE
> [INFO]
>
> [INFO] Compilation failure
> Failure executing javac, but could not parse the error:
>
>
> The system is out of resources.
> Consult the following stack trace for details.
> java.lang.OutOfMemoryError: Java heap space
>at
> com.sun.tools.javac.util.Position$LineMapImpl.build(Position.java:
> 139)
>at com.sun.tools.javac.util.Position.makeLineMap(Position.java:63)
>at com.sun.tools.javac.parser.Scanner.getLineMap(Scanner.java:1105)
>at
> com.sun.tools.javac.main.JavaCompiler.parse(JavaCompiler.java:512)
>at
> com.sun.tools.javac.main.JavaCompiler.parse(JavaCompiler.java:550)
>at
> com.sun.tools.javac.main.JavaCompiler.parseFiles(JavaCompiler.java:
> 801)
>at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:
> 727)
>at com.sun.tools.javac.main.Main.compile(Main.java:353)
>at com.sun.tools.javac.main.Main.compile(Main.java:279)
>at com.sun.tools.javac.main.Main.compile(Main.java:270)
>at com.sun.tools.javac.Main.compile(Main.java:87)
>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> 39)
>at
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
> 25)
>at java.lang.reflect.Method.invoke(Method.java:597)
>at
>
> org.codehaus.plexus.compiler.javac.JavacCompiler.compileInProcess(JavacCompiler.java:
> 420)
>at
>
> org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:
> 141)
>at
>
> org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:
> 493)
>at
> org.apache.maven.plugin.TestCompilerMojo.execute(TestCompilerMojo.java:
> 102)
>at
>
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:
> 443)
>at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:
> 539)
>at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:
> 480)
>at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:
> 459)
>at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:
> 311)
>at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:
> 278)
>at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:
> 143)
>at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
>at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
>at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> 39)
>at
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
> 25)
>
> with protobuf-2.3.0 everything was ok.
>
> Please, can anybody help me to resolve this problem.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Protocol Buffers" group.
> To post to this group, send email to protobuf@googlegroups.com.
> To unsubscribe from this group, send email to
> protobuf+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/protobuf?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" group.
To post to this group, send email to protobuf@googlegroups.com.
To unsubscribe from this group, send email to
protobuf+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/protobuf?hl=en.
