Our great sponsors
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
So why does Java close the channel when an "interrupt" happens? I looked at the git-blame of [1] to see if the commit message would explain it, but it's just been there since the first commit. The only other info is [2] but it doesn't elaborate the "IO safety issues". And are these interrupts just the underlying syscall returning EINTR or something Java-specific?
[1]: https://github.com/openjdk/jdk/blame/c313e1ac7b3305b1c012755...
[2]: https://stackoverflow.com/questions/1161297/
"AbstractInterruptibleChannel" seems to be doing this, and the comments/javadocs offer some hint. As to why they're designed this way, that's a good question.
https://github.com/openjdk-mirror/jdk7u-jdk/blob/master/src/...