RFR: JDK-8031445: Attach on windows can fail with java.io.IOException: All pipe instances are busy

[Chris Plummer]

Hi Gary,

I don't think you intended to include the ProblemList.txt changes in 
your webrev.

I think your changes address the "java.io.IOException: CreateNamedPipe 
failed" failures if a name collision is the cause. This failure mode was 
extremely rare (only 3 sightings), and if due to a collision, a single 
retry should suffice in making it not appear again in our lifetime. 
However, I don't think this addresses the "java.io.IOException: All pipe 
instances are busy" issue, which seems to the more common failures mode, 
although also very rare. Have you looked into its potential cause?

thanks,

Chris

On 2/7/18 8:51 AM, gary.adams at oracle.com wrote:
> The IOException that is observed when creating a new named pipe
> when the pipe already exists and is in use, recommends to retry
> the operation later. Since we are already using a random number
> to generate a unique pipe name, it makes sense to simply
> retry the operation with a new pipe name.
>
> Here is a proposed fix. Testing in progress.
>
>   Issue: https://bugs.openjdk.java.net/browse/JDK-8031445
>   Webrev: http://cr.openjdk.java.net/~gadams/8031445/
>
>