Occasionally see error appending to Chronicle Queue
See original GitHub issueOccasionally when running benchmarks, I see the exception below.
Versions:
openjdk version "14.0.2" 2020-07-14
OpenJDK Runtime Environment AdoptOpenJDK (build 14.0.2+12)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 14.0.2+12, mixed mode, sharing)
Darwin x.x.x.x 19.6.0 Darwin Kernel Version 19.6.0: Thu Jun 18 20:49:00 PDT 2020; root:xnu-6153.141.1~1/RELEASE_X86_64 x86_64
net.openhft:chronicle-queue:5.20.4
Exception:
07 Sep 2020 17:00:00.021 [Dummy Exchange] ERROR b.s.w.i.j.ChronicleQueueJournalWriter - Issue appending to Chronicle Queue
java.lang.IllegalStateException: Not the last released
at net.openhft.chronicle.core.io.VanillaReferenceCounted.releaseLast(VanillaReferenceCounted.java:110) ~[chronicle-queue-enterprise-all-2.19.352.jar:chronicle-bom:2.19.352]
at net.openhft.chronicle.core.io.AbstractReferenceCounted.releaseLast(AbstractReferenceCounted.java:123) ~[chronicle-queue-enterprise-all-2.19.352.jar:chronicle-bom:2.19.352]
at net.openhft.chronicle.bytes.MappedBytes.releaseLast(MappedBytes.java:853) ~[chronicle-queue-enterprise-all-2.19.352.jar:chronicle-bom:2.19.352]
at net.openhft.chronicle.core.io.ReferenceCounted.releaseLast(ReferenceCounted.java:67) ~[chronicle-queue-enterprise-all-2.19.352.jar:chronicle-bom:2.19.352]
at net.openhft.chronicle.queue.impl.single.StoreAppender.releaseBytesFor(StoreAppender.java:74) ~[chronicle-queue-enterprise-all-2.19.352.jar:chronicle-bom:2.19.352]
at net.openhft.chronicle.queue.impl.single.StoreAppender.resetWires(StoreAppender.java:258) ~[chronicle-queue-enterprise-all-2.19.352.jar:chronicle-bom:2.19.352]
at net.openhft.chronicle.queue.impl.single.StoreAppender.setCycle2(StoreAppender.java:237) ~[chronicle-queue-enterprise-all-2.19.352.jar:chronicle-bom:2.19.352]
at net.openhft.chronicle.queue.impl.single.StoreAppender.rollCycleTo(StoreAppender.java:592) ~[chronicle-queue-enterprise-all-2.19.352.jar:chronicle-bom:2.19.352]
at net.openhft.chronicle.queue.impl.single.StoreAppender.writingDocument(StoreAppender.java:336) ~[chronicle-queue-enterprise-all-2.19.352.jar:chronicle-bom:2.19.352]
at net.openhft.chronicle.queue.impl.single.StoreAppender.writingDocument(StoreAppender.java:310) ~[chronicle-queue-enterprise-all-2.19.352.jar:chronicle-bom:2.19.352]
at net.openhft.chronicle.queue.impl.single.StoreAppender.writeBytes(StoreAppender.java:93) ~[chronicle-queue-enterprise-all-2.19.352.jar:chronicle-bom:2.19.352]
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (7 by maintainers)
Top Results From Across the Web
Chronicle-Queue/FAQ.adoc at ea - GitHub
If you are seeing "OutOfMemoryError: Map failed". If you see the following error: Caused by: java.lang.
Read more >Chronicle Queue issue with certain boxes - Stack Overflow
All the boxes are in the same environment, I see that few boxes are seeing this exception and few are working fine. So...
Read more >Chronicle-Queue: Micro second messaging that stores ... - Gitee
Chronicle Queue manages storage by cycle. You can add a StoreFileListener which will notify you when a file is added, and when it...
Read more >Troubleshoot Dataflow errors - Google Cloud
If you run into problems with your Dataflow pipeline or job, this page lists error messages that you might see and provides suggestions...
Read more >Chronicle queue synchronous replication - Google Groups
You received this message because you are subscribed to the Google Groups "Chronicle" group. To unsubscribe from this group and stop receiving emails...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Can’t replicate on JDK 11. Still yet to run it with the tracing options.
@mikeb01 is this still an issue, I’m going to close it, but happy to reopen it if you feel it has not been resolved.