On Mon, 25 Mar 2024 13:15:48 GMT, Kevin Walls <kev...@openjdk.org> wrote:

> Test uses  jdk.test.lib.Utils.getFreePort() when launching a new Java command.
> Looks like it already recognises "java.rmi.server.ExportException: Port 
> already in use: " and retries, but there is a long-standing typo in the check.
> 
> e.g. 
> 
> test output:
> Error: Exception thrown by the agent: java.rmi.server.ExportException: Port 
> already in use: 37049; nested exception is: 
>       java.net.BindException: Address already in use
>       
> Test checks for:
>         !output.getOutput().contains("Exception thrown by the agent : 
> java.rmi.server.ExportException: Port already in use")
>               
> Oops, we have an extra space in there.  A day-one typo from JDK-7195249.
> 
> While here, try to clarify the while loop which recognises this port failure. 
>  Also add something to clarify which test(s) failed, and correct a comment in 
> test2 of AbstractFilePermissionTest.java

This pull request has now been integrated.

Changeset: 2af0312c
Author:    Kevin Walls <kev...@openjdk.org>
URL:       
https://git.openjdk.org/jdk/commit/2af0312c958e693b1377f4c014ae8f84cabf6b83
Stats:     19 lines in 1 file changed: 7 ins; 2 del; 10 mod

8328619: sun/management/jmxremote/bootstrap/SSLConfigFilePermissionTest.java 
failed with BindException: Address already in use

Reviewed-by: lmesnik, dfuchs

-------------

PR: https://git.openjdk.org/jdk/pull/18470

Reply via email to