RFR JDK-8225474: JDI connector accept fails "Address already in use" with concurrent listeners

[Alan Bateman]

On 17/06/2019 11:14, Andrew Leonard wrote:
> Thanks for the feedback Alan. I think i'm going to have to defer on 
> this issue for the moment, as I dont' have enough experience with JDI 
> usecases to accurately study this at the moment. I think you have also 
> demonstrated my "rustiness" in thread-safety issues, I think I will go 
> and brush up!!
>
> Should we create a separate bug to update the spec/doc to clarify the 
> position on JDI Connectors being non-thread-safe, or is the current 
> non-statement the normal stance on this one?
It wouldn't do any harm to add something to the javadoc to make it clear 
that Connectors are not safe for use by multiple concurrent threads and 
so need appropriate synchronization. There are "Thread safety" sections 
in several classes and something similar wouldn't look out of place here.

-Alan.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.java.net/pipermail/serviceability-dev/attachments/20190617/ae6bd747/attachment.html>