> 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
r 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
kung. 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
>&
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
> c
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
