Thanks Martin. My question was in fact not user-based but developer-based. I'm developing an alternative JUnit runner for Lucene/Solr builds and we hit lots of exceptional situations. Permgen errors are kind of hard to deal with because after you hit it there are very few recovery options (short of preloading all runner classes in advance).
Dawid On Wed, Jan 2, 2013 at 2:58 PM, Martin Gainty <mgai...@hotmail.com> wrote: > > David > > I was plagued by the same problem yesterday until I shut off forkMode in > maven-surefire-plugin e.g. > <build><plugins> <plugin> <artifactId>maven-surefire-plugin</artifactId> > <configuration> > <forkMode>never</forkMode></configuration> I also upped the MaxHeap and > PermGen params in _JAVA_OPTIONS environment variable e.g. > _JAVA_OPTIONS: -Xmx3192m -XX:MaxPermSize=3192m > Viel Gluck, > Martin > ______________________________________________ > Verzicht und Vertraulichkeitanmerkung > > Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger > sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung > oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich > dem Austausch von Informationen und entfaltet keine rechtliche > Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen > wir keine Haftung fuer den Inhalt uebernehmen. > > From: dawid.we...@gmail.com >> Date: Wed, 2 Jan 2013 09:33:20 +0100 >> Subject: Surefire and low memory conditions >> To: dev@maven.apache.org >> >> Hi. Just wanted to ping you because I remember we talked about >> hardnuts for test runners (like surefire). I've been recently trying >> to think of a way to shutdown the forked JVM cleanly on permgen/ OOM >> conditions (and signal it back as such to the controlling process). >> Seems to be quite hard because various JVMs appear to go crazy >> themselves when running under low memory. >> >> Anyway, out of curiousity I checked with surefire and it seems to hang >> for me (Windows, 8 core cpu). The code is here. >> https://github.com/dweiss/surefire-hardtests >> >> The single-threaded version says the forked VM shut down without >> saying good bye which seems like a fine resolution to me. This is >> hardly a "bug" in surefire -- like I mentioned, running anything with >> exhausted permgen or heap is very unpredictable in Java. Still, I'm >> curious if you see any workarounds or solutions for the issue. >> >> Dawid >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
