Compatibility issues on JDK 14

[sheinbergon]

Hi

sun.nio.ch.FileChannelImpl.map0 implementation has changed on JDK 14, requiring an additional boolean param.

This makes CQ unusable on that version of the JDK (works fine on JDK 13).

Tested with CQ version 5.19.2

[dpisklov]

@sheinbergon Chronicle's JDK support policy is linked to LTS versions. We support Java 8 and Java 11. So far, Oracle hasn't announced any LTS versions past Java 11 so we do not intend to support newer versions until there is an LTS version.
That said, we are happy to accept PRs.

[sheinbergon]

@dpisklov Thank you for your response.
Next LTS version would be JDK 17 ( a year and half from now).
When that version arrives, you're going to meet that error I just mentioned.

I'll see if it's complicated to fix it myself or not and let you know.

[sheinbergon]

@dpisklov Opened this PR to provide initial support for JDK 14, tested locally and seems to be fine.

[sheinbergon]

@dpisklov any response?

[dpisklov]

@sheinbergon sorry it was a bank holiday in the UK.
I merged the PR.

[dpisklov]

@sheinbergon can we close this?

[sheinbergon]

@dpisklov any chance to release a new version for the Chronicle-Core and this project pointing to the aforementioned with that fix merged?

10x

[dpisklov]

@sheinbergon
Done.

Chronicle-BOM : 2.19.116

chronicle-core: 2.19.4

• Improve EventHandler termination performance [IndexedChronicle TCP replication not working #101]
• Compatibility issues on JDK 14 [CHRON-79 - VanillaChronicle's ExcerpAppender does not set proper capacit... #100]

chronicle-queue: 5.19.11

• Fixed ARM compatibility [Fixed ARM compatibility #656]
• Memory leak in DiskSpaceMoniotor inside SingleChronicleQueue.java [Memory leak in DiskSpaceMoniotor inside SingleChronicleQueue.java #630]