Lines Matching defs:LogManager
40 * There is a single global LogManager object that is used to
43 * This LogManager object:
52 * The global LogManager object can be retrieved using LogManager.getLogManager().
53 * The LogManager object is created during class initialization and
56 * At startup the LogManager class is located using the
59 * By default, the LogManager reads its initial configuration from
64 * In addition, the LogManager uses two optional system properties that
80 * to define properties in the LogManager.
88 * above, the LogManager will read its initial configuration from
125 * Note that all classes loaded during LogManager configuration are
127 * That includes the LogManager class, any config classes, and any
143 * All methods on the LogManager object are multi-thread safe.
148 public class LogManager {
149 // The global LogManager object
150 private static LogManager manager;
154 = new PropertyChangeSupport(LogManager.class);
181 manager = (LogManager) clz.newInstance();
184 manager = (LogManager) clz.newInstance();
192 manager = new LogManager();
206 // would deadlock with the LogManager.<clinit>.
235 // This is to ensure the LogManager.<clinit> is completed
237 LogManager mgr = manager;
241 synchronized (LogManager.this) {
256 * it is intended that there only be one LogManager object, whose value is
259 protected LogManager() {
270 * Return the global LogManager object.
272 public static LogManager getLogManager() {
396 // in the LogManager global namespace.
401 // This method must delegate to the LogManager implementation to
403 // as a LogManager subclass may override the addLogger, getLogger,
438 // Add the system logger to the LogManager's namespace if not exist
445 // This would avoid potential bug in custom LogManager.getLogger
455 // LogManager will set the sysLogger's handlers via LogManager.addLogger method.
472 // The default LogManager implementation has one system context and user
493 // a LogManager subclass may have its own implementation to add and
494 // get a Logger. So delegate to the LogManager to do the work.
660 // note: all calls to removeLogger are synchronized on LogManager's
738 // in the LogManager's namespace if not exist so that there is only
820 // LogManager.namedLoggers
825 // LogManager.LogNode.loggerRef
913 // haven't finished loading LogManager yet
934 * object to avoid it being garbage collected. The LogManager
1023 * to {@code LogManager.getLogger()}, then the caller must check the
1024 * return value from {@code LogManager.getLogger()} for null to properly