I believe the circumstances are that our test automation software deleted the journal files, causing a prior journal I/O operation to fail with an IOException, specifically in the JournalManager#writeTransactionToJournal method. That exception left the transaction ByteBuffer in a flipped condition; the buffer.clear() method was never called.
In summary, I think this bug requires an extraordinary event (deleting the journal files of the running server), but the consequence also needs to be handled better.
I believe the circumstances are that our test automation software deleted the journal files, causing a prior journal I/O operation to fail with an IOException, specifically in the JournalManager# writeTransactio nToJournal method. That exception left the transaction ByteBuffer in a flipped condition; the buffer.clear() method was never called.
In summary, I think this bug requires an extraordinary event (deleting the journal files of the running server), but the consequence also needs to be handled better.