RFR: JDK-8203364: Some serviceability/sa/ tests intermittently fail with java.io.IOException: LingeredApp terminated with non-zero exit code 3
Chris Plummer
chris.plummer at oracle.com
Tue Apr 2 17:58:07 UTC 2019
Hi Gary,
I see various System.exit() calls with varying exit status. Is there
some place that documents them? What is 4?
Any reason not to print the exception before doing the System.exit(4)?
thanks,
Chris
On 4/2/19 4:50 AM, Gary Adams wrote:
> This proposed change allows a wider range of IOExceptions to be observed
> when a LingeredApp is being shutdown. It may not be just a
> NoSuchFileException.
> Botton line - if the lock file doesn't exist at the time the IOException
> is observed then the main application is terminating the test sequence
> and LingeredApp should end normally.
>
> Webrev: http://cr.openjdk.java.net/~gadams/8203364/webrev/
> Issue: https://bugs.openjdk.java.net/browse/JDK-8203364
More information about the serviceability-dev
mailing list