use ConcurrentHashMap to replace Collections.synchronizedMap(HashMap) ?

Xeno Amess xenoamess at gmail.com
Wed Apr 20 18:26:18 UTC 2022

Previous message (by thread): Fwd: RFR:8235211: serviceability/attach/RemovingUnixDomainSocketTest.java fails with AttachNotSupportedException: Unable to open socket file
Next message (by thread): use ConcurrentHashMap to replace Collections.synchronizedMap(HashMap) ?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Collections.synchronizedMap(new HashMap<Integer, byte[]>())

new ConcurrentHashMap <Integer, byte[]>  ()

Is the later one always better than the first one?

I personally think so, but are there any traps in it?

Previous message (by thread): Fwd: RFR:8235211: serviceability/attach/RemovingUnixDomainSocketTest.java fails with AttachNotSupportedException: Unable to open socket file
Next message (by thread): use ConcurrentHashMap to replace Collections.synchronizedMap(HashMap) ?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the jdk-dev mailing list