maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alonso Isidoro Roman <alons...@gmail.com>
Subject Re: Failsafe: Killing self fork JVM. PING timeout elapsed.
Date Sat, 23 Feb 2019 13:07:37 GMT
unsubscribe

El sáb., 23 feb. 2019 a las 13:36, Tibor Digana (<tibordigana@apache.org>)
escribió:

> Hi Jason,
>
> We spoke about this issue on our chat in ASF Slack:
> "I think his tests have been paused for a long GC periods and timed out 3x
> PING period = 30 seconds. After this period forked JVM supposed the Maven
> process was killed by JenkinsCI and therefore all surefire processes are
> killed as well and all the file handlers and memory consumptions are
> freed."
>
> "But I have to say that `-Xmx3g` may cause long GC cycles, see
>
> https://maven.apache.org/surefire/maven-surefire-plugin/examples/shutdown.html
> "
>
> You are using java-1.8-openjdk. I guess you should use Shenandoah GC which
> is an experimental algorithm in  JVM 1.8. This would significantly short
> the GC cycles.
>
> We should of cource provide a new configuration parameter to give you a
> chance to prolong the PING.
>
> Cheers
> Tibor
>


-- 
Alonso Isidoro Roman
[image: https://]about.me/alonso.isidoro.roman
<https://about.me/alonso.isidoro.roman?promo=email_sig&utm_source=email_sig&utm_medium=email_sig&utm_campaign=external_links>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message