Details
Description
This bug has very simple workarounds. It will probably be fixed in the next major release.
Report by William Pietri:
> Suppose in version 1 of the software I have a bunch of transaction
> A. In version 2, this transaction is removed. It seems like even if
> I snapshot as the last thing before shutdown and upgrade, Prevayler
> will still read the last journal, even though it doesn't need to.
> Won't this result in a ClassNotFoundException as it tries to load
> and discard the copies of transaction A in the journal?
Workarounds:
1) To keep the class of Transaction A around, even if it is no longer being used.
OR
2) To delete or move the old journal files to another directory.
Issue Links
- relates to
-
PRV-22
Unified "Serializer" interface
-
Ooh! The chunked encoding scheme I just described for
PRV-22would eliminate this problem as well, since transactions can be counted and skipped without actually deserializing them at all.