On Wednesday, December 3, 2014 3:57:21 PM UTC+1, Eduard Català wrote:
Tank you Thomas,But restarting Jetty Server button does not work properly: At third redeploy (50MB of jar libraries) an OutOfMemoryError is thrown, i suspect that embedded jetty server is not properly restarted (only reloads context without stopping entire server).
Then you could use a third-party, independent server, and run SDM on its own (pointing -launcherDir to the webapp directory used by the other server so that "compile on load" works; or using the "Dev Mode On" and "Dev Mode Off" bookmarklets).
Note that I don't think Jetty leaks memory, but there are libraries that leak memory by artificially keeping the old ClassLoader in memory and preventing it being garbage-collected. One such library is Guice (through Guava); see https://github.com/tbroyer/gwt-maven-archetypes/issues/19
There could also be leaks if your webapp happens to pass some object to a class in the parent classloader that would retain it (e.g. putting it in a static field), preventing the whole webapp ClassLoader from being garbage-collected.
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment