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

Bernd Eckenfels ecki at zusammenkunft.net
Fri Jun 7 16:45:49 UTC 2019


 stopListening seems not atomically using listenMap. (Ie change get/remove to remove only)

BTW this would be a good usecase for a CopyOnWriteMap...


--
http://bernd.eckenfels.net

________________________________
Von: core-libs-dev <core-libs-dev-bounces at openjdk.java.net> im Auftrag von Andrew Leonard <andrew_m_leonard at uk.ibm.com>
Gesendet: Freitag, Juni 7, 2019 6:14 PM
An: core-libs-dev at openjdk.java.net
Betreff: RFR 8225474: JDI connector accept fails "Address already in use" with concurrent listeners

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

Thanks
Andrew

Andrew Leonard
Java Runtimes Development
IBM Hursley
IBM United Kingdom Ltd
internet email: andrew_m_leonard at uk.ibm.com

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU



More information about the core-libs-dev mailing list