Major On some instances, customers can get a short regular intervals messages of the type:
2021-05-31T12:47:07,923 WARN [background~resource~releaser] [net.openhft.chronicle.core.io.BackgroundResourceReleaser] Failed in release/close net.openhft.chronicle.core.io.ClosedIllegalStateException: Released at net.openhft.chronicle.core.io.VanillaReferenceCounted.release(VanillaReferenceCounted.java:83) ~[chronicle-core-2.20.21.jar:?] at net.openhft.chronicle.core.io.AbstractReferenceCounted.release(AbstractReferenceCounted.java:118) ~[chronicle-core-2.20.21.jar:?] at net.openhft.chronicle.core.io.AbstractCloseableReferenceCounted.release(AbstractCloseableReferenceCounted.java:42) ~[chronicle-core-2.20.21.jar:?] at net.openhft.chronicle.bytes.MappedBytes.performRelease(MappedBytes.java:536) ~[chronicle-bytes-2.20.10.jar:2.20.10] at net.openhft.chronicle.core.io.BackgroundResourceReleaser.performRelease(BackgroundResourceReleaser.java:79) ~[chronicle-core-2.20.21.jar:?] at net.openhft.chronicle.core.io.BackgroundResourceReleaser.runReleaseResources(BackgroundResourceReleaser.java:28) ~[chronicle-core-2.20.21.jar:?] at java.lang.Thread.run(Thread.java:829) [?:?]
This exactly matches the description of https://github.com/OpenHFT/Chronicle-Bytes/issues/157 fixed on June 25th, 2021.
There is also https://github.com/OpenHFT/Chronicle-Core/issues/173, implemented in December, 16th, 2020, which should help diagnosing the problem, if not fixed.
Thus, the need to consider the upgrade of Chronicle Queue to a more recent version, later than June 2021, e.g. version 5.21.89 with all its support libraries.
- Is referenced in
