Uses of Class
journal.io.api.ClosedJournalException

Packages that use ClosedJournalException

journal.io.api

Uses of ClosedJournalException in journal.io.api

Methods in journal.io.api that throw ClosedJournalException

void	Journal.compact() Compact the journal, reducing size of logs containing deleted entries and completely removing empty (with only deleted entries) logs.
void	Journal.delete(Location location) Delete the record at the given Location. Deletes cause first a batch sync and always are logical: records will be actually deleted at log cleanup time.
byte[]	Journal.read(Location location, Journal.ReadType read) Read the record stored at the given Location, either by syncing with the disk state (if ReadType.SYNC) or by taking advantage of speculative disk reads (if ReadType.ASYNC); the latter is faster, while the former is slower but will suddenly detect deleted records.
Iterable<Location>	Journal.redo() Return an iterable to replay the journal by going through all records locations.
Iterable<Location>	Journal.redo(Location start) Return an iterable to replay the journal by going through all records locations starting from the given one.
void	Journal.sync() Sync asynchronously written records on disk.
Iterable<Location>	Journal.undo() Return an iterable to replay the journal in reverse, starting with the newest location and ending with the first.
Iterable<Location>	Journal.undo(Location end) Return an iterable to replay the journal in reverse, starting with the newest location and ending with the specified end location.
Location	Journal.write(byte[] data, Journal.WriteType write) Write the given byte buffer record, either sync (if WriteType.SYNC) or async (if WriteType.ASYNC), and returns the stored Location. A sync write causes all previously batched async writes to be synced too.
Location	Journal.write(byte[] data, Journal.WriteType write, WriteCallback callback) Write the given byte buffer record, either sync (if WriteType.SYNC) or async (if WriteType.ASYNC), and returns the stored Location. A sync write causes all previously batched async writes to be synced too. The provided callback will be invoked if sync is completed or if some error occurs during syncing.