> It would be quite simple to have a thread in the forked process
> simply pulsing a heartbeat back to the plugin ?
>
> And if 3 heartbeats are missed, we simply kill it ? (Pardon the pun ;)
Yeah, I sort of have that already but not in a background thread form
(it's a longer story). Anyway, a back
It would be quite simple to have a thread in the forked process
simply pulsing a heartbeat back to the plugin ?
And if 3 heartbeats are missed, we simply kill it ? (Pardon the pun ;)
Kristian
2013/1/2 Dawid Weiss :
> Hi. Just wanted to ping you because I remember we talked about
> hardnuts for
Martin,
you can also use the argLine property in the Surefire configuration to
pass appropriate -X* settings to the forked processes. That way you can use
any fork mode you might want and not have to pollute the general java opts
and, more importantly, the memory realm of a multi-module build (if
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
David
I was plagued by the same problem yesterday until I shut off forkMode in
maven-surefire-plugin e.g.
maven-surefire-plugin
never I also upped the MaxHeap and
PermGen params in _JAVA_OPTIONS environment variable e.g.
_JAVA_OPTIONS: -Xmx3192m -XX:MaxPermSize=3192m
Viel Gluck,
Martin
___
