maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Young <jason.yo...@procentive.com>
Subject Re: Failsafe: Killing self fork JVM. PING timeout elapsed.
Date Tue, 26 Feb 2019 16:16:32 GMT
Thanks for the information. It's good to see someone understands a little
about this.

Incidentally, we have been looking at other GCs and VMs for the application
in production environments, so I'll look into how these affect tests as
well. I'll try to enable some logging about GC pauses to see what's up.

How would `-Xmx3g` cause long GC cycles? Do you think the value is simply
too low?

FWIW we're running the Maven build in an Alpine-based Docker container.

On Sat, Feb 23, 2019 at 6:36 AM Tibor Digana <tibordigana@apache.org> wrote:

> 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
>


-- 

Jason Young

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