This content has been marked as final. Show 3 replies
Our apologies, this is our bug. This can only happen if JE is killed off when the log is less than 605 bytes, before the standard first checkpoint is written. JE should never fail at recovery time in this way.
In this case, the log has no user data at all, and only holds the beginning of JE internal structures. You can safely remove the log file to restart in this case. We'll also contact you shortly with a fix for the problem. The fix is trivial, frankly all the time will be in writing a unit test.
Thanks for the quick reply. Is there a workaround available? Maybe a config value we can set to avoid this scenario?
Is there a workaround
available? Maybe a config value we can set to avoidNo, I'm afraid there's no workaround. However, the way to recognize this case is that the log has less than 1345 bytes (not the 605 I reported earlier), and in the case, can be moved aside with no loss of data.
The next patch release will contain this fix, and it will be labeled in the change log with the tag [#16016]