Hi,
there's been a history of deadlocks when attempting to close() various
streams which predates OpenJDK bug and source history, so I believe
having close synchronize on this is a bad idea. This move from
AtomicBoolean to a volatile for signaling should be semantically neutral
and more or
probably not called that often anyway)
Gruss
Bernd
--
http://bernd.eckenfels.net
Von: Bernd Eckenfels
Gesendet: Montag, 8. Oktober 2018 21:28
An: core-libs-dev
Betreff: AW: RFR: 8211859: (fc) Avoid initializing
AtomicBooleanfromRandomAccessFile
getChannel() Synchronizes only on `this` and `close
