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

Alan Bateman Alan.Bateman at oracle.com
Fri Jun 7 14:08:16 UTC 2019


On 07/06/2019 14:43, Andrew Leonard wrote:
> Hi,
> Please can I request a sponsor and review of this patch for JDK-8225474. A
> problem that we have seen intermittently with JDI connector stress tests
> for quite a while that is caused by an non-thread safe HashMap in the
> connector class. I've created a standalone testcase that reproduces it
> reliably.
>      http://cr.openjdk.java.net/~aleonard/8225474/webrev.00
>
Probably best to bring this to serviceability-dev as that is where the 
JDI and the other debugger interfaces are maintained. I think the main 
issue here is that Connectors are not specified to be thread safe. There 
may be spec changes needed here as minimally it should be possible for a 
ListeningConnector that supports multiple connections to hand off a 
VirtualMachine when a debuggee connects.

-Alan


More information about the core-libs-dev mailing list