Hi
The problem is that you *only* specify the initial and maximum heap size
and leave the permanent generation space to be the default. Look at the
options Claus has already provided by his reply and try again (...
-XX:MaxPermSize=512m).
Babak
Am 17.01.14 18:20 schrieb "MichaelAtSAG" unter :
I do not understand what this means.
--
View this message in context:
http://camel.465427.n5.nabble.com/JVM-is-running-out-of-memory-during-full-Camel-build-tp5746106p5746166.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Build still complaining about memory. It works if I disable the camel-web
module:
--
View this message in context:
http://camel.465427.n5.nabble.com/JVM-is-running-out-of-memory-during-full-Camel-build-tp5746106p5746165.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Make sure, also, in your maven pom that i you are forking the VM for
testing that you provide the forked VM with enough memory. The Maven opts
will not be propagated to the forked VM so beware of that.
*Robert Simmons Jr. MSc. - Lead Java Architect @ EA*
*Author of: Hardcore Java (2003) and Mainta
I have these maven opts and build with maven 3.0.4 and it works fine
declare -x MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=512m"
On Thu, Jan 16, 2014 at 10:05 PM, MichaelAtSAG wrote:
> I ran it again with 2GB and hit compile exception at same point:
>
> set MAVEN_OPTS=-Xms528m -Xmx2024m
>
> Failure:
>
I ran it again with 2GB and hit compile exception at same point:
set MAVEN_OPTS=-Xms528m -Xmx2024m
Failure:
[INFO]
[INFO] Building Camel :: Web 2.13-SNAPSHOT
[INFO]
--
