Javarebel will certainly help here, but it wont solve the problem
entirely as there are always going to be somethings that it cannot
replace dynamically.
Regarding the question about goals, this is the maven syntax:
mvn goal goal... etc
so, install, and jetty:run are goals in maven
A colleague of mine found these interesting articles regarding PerGen issues :
http://blogs.sun.com/fkieviet/entry/classloader_leaks_the_dreaded_java
http://blogs.sun.com/fkieviet/entry/how_to_fix_the_dreaded
~Rob
--~--~-~--~~~---~--~~
You received this
Alex,
Any reason your running the install goal? You really don't need to.
Regarding the permgen: Can you show your maven options? You can
improve the situation by setting a larger heap size, however this is
an unfortunate thing that just goes along with jetty and maven.
HTH
Cheers, Tim
On
Hi,
Is this error occurring after a context reload? You may want to turn
off context reloading in your mvn jetty configuration because, as far
as i can tell, that has always been a completely broken feature.
Do this by adding scanIntervalSeconds0/scanIntervalSeconds to the
org.mortbay.jetty
Hi Tim, I'm not sure even what install goal means. I'm new to Maven,
Jetty and Scala, so I'm following examples I've read. Whats the
better approach here?
export MAVEN_OPTS=-Xms256m -Xmx1024m
On Oct 8, 2:16 pm, Timothy Perrett timo...@getintheloop.eu wrote:
Alex,
Any reason your running the
Hi Jon,
I haven't narrowed it down to being after a context reload or not.
I'll try what you suggested and turn off jetty's reload and use
javaRebel instead.
Where would I set those JVM flags, should those go in MAVEN_OPTS?
I'll keep SBT in mind...
- ALex
On Oct 8, 4:37 pm, jon
Yes,
I think this will get you going with javarebel:
MAVEN_OPTS=-XX:+CMSClassUnloadingEnabled -XX:MaxPermSize=128m -
Xmx512m -noverify -javaagent:/path/to/jrebel-2.1/jrebel.jar mvn
jetty:run
in another terminal window
mvn scala:cc
get a free license here:
