All Classes and Interfaces
Class
Description
An implementation of LogBuffer that
provides features necessary for a reliable Transaction Monitor
journal.
An implementation of BlockLogBuffer that does *not* perform IO.
Provides configuration information for a
Logger
instance.Exception thrown when LogFileManager.open() detects an
invalid file set.
Exception thrown when Logger detects a journal block
with invalid content.
Exception thrown when XAJournalReader detects a journal block with an invalid
header.
Exception thrown when XAJournalReader detects a journal block with an invalid
header.
Classes used as buffers in LogBufferManager must implement this interface.
Provides a generalized buffer manager for journals and loggers.
Defines valid values for LogBuffer status.
Checked exception thrown when put is called after the log has been
closed.
This interface is implemented by users of the Logger.
Base exception class for HOWL exceptions.
An individual file within a set of log files managed by a Logger.
Defines the header record for a LogFile.
Manage a set of log files.
Checked exception thrown when the Logger
attempts to switch to an alternate log file that
contains the active mark.
Manage a configured set of two or more physical log files.
Not Implemented.
base class for all log objects that require
configuration information.
LogRecord class used by Logger.replay().
Checked exception thrown when the byte[] passed to put
is larger than the configured buffer size.
Define record types used by Logger implementations.
Manage state variables for the Logger instance.
Objects that wish to read a log must implement the ReplayListener interface.
XA Transaction Managers write log records using the XALogger subclass of
the basic HOWL Logger.
A specialized subclass of
Logger
intended to provide functionality required by any XA Transaction Manager.private class used by XALogger.replay() methods.
Extends
LogRecord
with
members that are specific to XALogger.