Package Summary Overview Summary

### class:LogManager [CHANGED]
-     public class LogManager
      extends Object
There is a single global LogManager object that is used to maintain a set of shared state about Loggers and log services. This LogManager object: Manages a hierarchical namespace of Logger objects. All named Loggers are stored in this namespace. Manages a set of logging control properties. These are simple key-value pairs that can be used by Handlers and other logging objects to configure themselves. The global LogManager object can be retrieved using LogManager.getLogManager(). The LogManager object is created during class initialization and cannot subsequently be changed. At startup the LogManager class is located using the java.util.logging.manager system property. The LogManager defines two optional system properties that allow control over the initial configuration: "java.util.logging.config.class" "java.util.logging.config.file" These two properties may be specified on the command line to the "java" command, or as system property definitions passed to JNI_CreateJavaVM. If the "java.util.logging.config.class" property is set, then the property value is treated as a class name. The given class will be loaded, an object will be instantiated, and that object's constructor is responsible for reading in the initial configuration. (That object may use other system properties to control its configuration.) The alternate configuration class can use `readConfiguration(InputStream)` to define properties in the LogManager. If "java.util.logging.config.class" property is not set, then the "java.util.logging.config.file" system property can be used to specify a properties file (in java.util.Properties format). The initial logging configuration will be read from this file. If neither of these properties is defined then the LogManager uses its default configuration. The default configuration is typically loaded from the properties file "`libconf/logging.properties`" in the Java installation directory. The properties for loggers and Handlers will have names starting with the dot-separated name for the handler or logger. The global logging properties may include: A property "handlers". This defines a whitespace or comma separated list of class names for handler classes to load and register as handlers on the root Logger (the Logger named ""). Each class name must be for a Handler class which has a default constructor. Note that these Handlers may be created lazily, when they are first used. A property "<logger>.handlers". This defines a whitespace or comma separated list of class names for handlers classes to load and register as handlers to the specified logger. Each class name must be for a Handler class which has a default constructor. Note that these Handlers may be created lazily, when they are first used. A property "<logger>.useParentHandlers". This defines a boolean value. By default every logger calls its parent in addition to handling the logging message itself, this often result in messages being handled by the root logger as well. When setting this property to false a Handler needs to be configured for this logger otherwise no logging messages are delivered. A property "config". This property is intended to allow arbitrary configuration code to be run. The property defines a whitespace or comma separated list of class names. A new instance will be created for each named class. The default constructor of each class may execute arbitrary code to update the logging configuration, such as setting logger levels, adding handlers, adding filters, etc. Note that all classes loaded during LogManager configuration are first searched on the system class path before any user class path. That includes the LogManager class, any config classes, and any handler classes. Loggers are organized into a naming hierarchy based on their dot separated names. Thus "a.b.c" is a child of "a.b", but "a.b1" and a.b2" are peers. All properties whose names end with ".level" are assumed to define log levels for Loggers. Thus "foo.level" defines a log level for the logger called "foo" and (recursively) for any of its children in the naming hierarchy. Log Levels are applied in the order they are defined in the properties file. Thus level settings for child nodes in the tree should come after settings for their parents. The property name ".level" can be used to set the level for the root of the tree. All methods on the LogManager object are multi-thread safe. Since: 1.4
-     public class LogManager
      extends Object
- There is a single global LogManager object that is used to maintain a set of shared state about Loggers and log services. This LogManager object: Manages a hierarchical namespace of Logger objects. All named Loggers are stored in this namespace. Manages a set of logging control properties. These are simple key-value pairs that can be used by Handlers and other logging objects to configure themselves. The global LogManager object can be retrieved using LogManager.getLogManager(). The LogManager object is created during class initialization and cannot subsequently be changed. At startup the LogManager class is located using the java.util.logging.manager system property. The LogManager defines two optional system properties that allow control over the initial configuration: "java.util.logging.config.class" "java.util.logging.config.file" These two properties may be specified on the command line to the "java" command, or as system property definitions passed to JNI_CreateJavaVM. If the "java.util.logging.config.class" property is set, then the property value is treated as a class name. The given class will be loaded, an object will be instantiated, and that object's constructor is responsible for reading in the initial configuration. (That object may use other system properties to control its configuration.) The alternate configuration class can use `readConfiguration(InputStream)` to define properties in the LogManager. If "java.util.logging.config.class" property is not set, then the "java.util.logging.config.file" system property can be used to specify a properties file (in java.util.Properties format). The initial logging configuration will be read from this file. If neither of these properties is defined then the LogManager uses its default configuration. The default configuration is typically loaded from the properties file "`lib/logging.properties`" in the Java installation directory. The properties for loggers and Handlers will have names starting with the dot-separated name for the handler or logger. The global logging properties may include: A property "handlers". This defines a whitespace or comma separated list of class names for handler classes to load and register as handlers on the root Logger (the Logger named ""). Each class name must be for a Handler class which has a default constructor. Note that these Handlers may be created lazily, when they are first used. A property "<logger>.handlers". This defines a whitespace or comma separated list of class names for handlers classes to load and register as handlers to the specified logger. Each class name must be for a Handler class which has a default constructor. Note that these Handlers may be created lazily, when they are first used. A property "<logger>.useParentHandlers". This defines a boolean value. By default every logger calls its parent in addition to handling the logging message itself, this often result in messages being handled by the root logger as well. When setting this property to false a Handler needs to be configured for this logger otherwise no logging messages are delivered. A property "config". This property is intended to allow arbitrary configuration code to be run. The property defines a whitespace or comma separated list of class names. A new instance will be created for each named class. The default constructor of each class may execute arbitrary code to update the logging configuration, such as setting logger levels, adding handlers, adding filters, etc. Note that all classes loaded during LogManager configuration are first searched on the system class path before any user class path. That includes the LogManager class, any config classes, and any handler classes. Loggers are organized into a naming hierarchy based on their dot separated names. Thus "a.b.c" is a child of "a.b", but "a.b1" and a.b2" are peers. All properties whose names end with ".level" are assumed to define log levels for Loggers. Thus "foo.level" defines a log level for the logger called "foo" and (recursively) for any of its children in the naming hierarchy. Log Levels are applied in the order they are defined in the properties file. Thus level settings for child nodes in the tree should come after settings for their parents. The property name ".level" can be used to set the level for the root of the tree. All methods on the LogManager object are multi-thread safe. Since: 1.4 |
      public class LogManager
      extends Object
There is a single global LogManager object that is used to maintain a set of shared state about Loggers and log services. This LogManager object: Manages a hierarchical namespace of Logger objects. All named Loggers are stored in this namespace. Manages a set of logging control properties. These are simple key-value pairs that can be used by Handlers and other logging objects to configure themselves. The global LogManager object can be retrieved using LogManager.getLogManager(). The LogManager object is created during class initialization and cannot subsequently be changed. At startup the LogManager class is located using the java.util.logging.manager system property. The LogManager defines two optional system properties that allow control over the initial configuration: "java.util.logging.config.class" "java.util.logging.config.file" These two properties may be specified on the command line to the "java" command, or as system property definitions passed to JNI_CreateJavaVM. If the "java.util.logging.config.class" property is set, then the property value is treated as a class name. The given class will be loaded, an object will be instantiated, and that object's constructor is responsible for reading in the initial configuration. (That object may use other system properties to control its configuration.) The alternate configuration class can use `readConfiguration(InputStream)` to define properties in the LogManager. If "java.util.logging.config.class" property is not set, then the "java.util.logging.config.file" system property can be used to specify a properties file (in java.util.Properties format). The initial logging configuration will be read from this file. If neither of these properties is defined then the LogManager uses its default configuration. The default configuration is typically loaded from the properties file "`conf/logging.properties`" in the Java installation directory. The properties for loggers and Handlers will have names starting with the dot-separated name for the handler or logger. The global logging properties may include: A property "handlers". This defines a whitespace or comma separated list of class names for handler classes to load and register as handlers on the root Logger (the Logger named ""). Each class name must be for a Handler class which has a default constructor. Note that these Handlers may be created lazily, when they are first used. A property "<logger>.handlers". This defines a whitespace or comma separated list of class names for handlers classes to load and register as handlers to the specified logger. Each class name must be for a Handler class which has a default constructor. Note that these Handlers may be created lazily, when they are first used. A property "<logger>.useParentHandlers". This defines a boolean value. By default every logger calls its parent in addition to handling the logging message itself, this often result in messages being handled by the root logger as well. When setting this property to false a Handler needs to be configured for this logger otherwise no logging messages are delivered. A property "config". This property is intended to allow arbitrary configuration code to be run. The property defines a whitespace or comma separated list of class names. A new instance will be created for each named class. The default constructor of each class may execute arbitrary code to update the logging configuration, such as setting logger levels, adding handlers, adding filters, etc. Note that all classes loaded during LogManager configuration are first searched on the system class path before any user class path. That includes the LogManager class, any config classes, and any handler classes. Loggers are organized into a naming hierarchy based on their dot separated names. Thus "a.b.c" is a child of "a.b", but "a.b1" and a.b2" are peers. All properties whose names end with ".level" are assumed to define log levels for Loggers. Thus "foo.level" defines a log level for the logger called "foo" and (recursively) for any of its children in the naming hierarchy. Log Levels are applied in the order they are defined in the properties file. Thus level settings for child nodes in the tree should come after settings for their parents. The property name ".level" can be used to set the level for the root of the tree. All methods on the LogManager object are multi-thread safe. Since: 1.4

### field:LOGGING_MXBEAN_NAME [NONE]
- #### LOGGING_MXBEAN_NAME
      public static final String LOGGING_MXBEAN_NAME
String representation of the `ObjectName` for the management interface for the logging facility. Since: 1.5 See Also: `PlatformLoggingMXBean`, `LoggingMXBean`, Constant Field Values

### constructor:LogManager() [NONE]
- #### LogManager
      protected LogManager()
Protected constructor. This is protected so that container applications (such as J2EE containers) can subclass the object. It is non-public as it is intended that there only be one LogManager object, whose value is retrieved by calling LogManager.getLogManager.

### method:getLogManager() [NONE]
- #### getLogManager
      public static LogManager getLogManager()
Returns the global LogManager object. Returns: the global LogManager object

### method:addLogger(java.util.logging.Logger) [NONE]
- #### addLogger
      public boolean addLogger(Logger logger)
Add a named logger. This does nothing and returns false if a logger with the same name is already registered. The Logger factory methods call this method to register each newly created Logger. The application should retain its own reference to the Logger object to avoid it being garbage collected. The LogManager may only retain a weak reference. Parameters: `logger` - the new logger. Returns: true if the argument logger was registered successfully, false if a logger of that name already exists. Throws: `NullPointerException` - if the logger name is null.

### method:getLogger(java.lang.String) [NONE]
- #### getLogger
      public Logger getLogger(String name)
Method to find a named logger. Note that since untrusted code may create loggers with arbitrary names this method should not be relied on to find Loggers for security sensitive logging. It is also important to note that the Logger associated with the String `name` may be garbage collected at any time if there is no strong reference to the Logger. The caller of this method must check the return value for null in order to properly handle the case where the Logger has been garbage collected. Parameters: `name` - name of the logger Returns: matching logger or null if none is found

### method:getLoggerNames() [NONE]
- #### getLoggerNames
      public Enumeration<String> getLoggerNames()
Get an enumeration of known logger names. Note: Loggers may be added dynamically as new classes are loaded. This method only reports on the loggers that are currently registered. It is also important to note that this method only returns the name of a Logger, not a strong reference to the Logger itself. The returned String does nothing to prevent the Logger from being garbage collected. In particular, if the returned name is passed to `LogManager.getLogger()`, then the caller must check the return value from `LogManager.getLogger()` for null to properly handle the case where the Logger has been garbage collected in the time since its name was returned by this method. Returns: enumeration of logger name strings

### method:readConfiguration() [NONE]
- #### readConfiguration
      public void readConfiguration()
                             throws IOException,
                                    SecurityException
Reinitialize the logging properties and reread the logging configuration. The same rules are used for locating the configuration properties as are used at startup. So normally the logging properties will be re-read from the same file that was used at startup. Any log level definitions in the new configuration file will be applied using Logger.setLevel(), if the target Logger exists. Any registered configuration listener will be invoked after the properties are read. Throws: `SecurityException` - if a security manager exists and if the caller does not have LoggingPermission("control"). `IOException` - if there are IO problems reading the configuration.

### method:reset() [NONE]
- #### reset
      public void reset()
                 throws SecurityException
Reset the logging configuration. For all named loggers, the reset operation removes and closes all Handlers and (except for the root logger) sets the level to null. The root logger's level is set to Level.INFO. Throws: `SecurityException` - if a security manager exists and if the caller does not have LoggingPermission("control").

### method:readConfiguration(java.io.InputStream) [NONE]
- #### readConfiguration
      public void readConfiguration(InputStream ins)
                             throws IOException,
                                    SecurityException
Reinitialize the logging properties and reread the logging configuration from the given stream, which should be in java.util.Properties format. Any registered configuration listener will be invoked after the properties are read. Any log level definitions in the new configuration file will be applied using Logger.setLevel(), if the target Logger exists. Parameters: `ins` - stream to read properties from Throws: `SecurityException` - if a security manager exists and if the caller does not have LoggingPermission("control"). `IOException` - if there are problems reading from the stream.

### method:getProperty(java.lang.String) [NONE]
- #### getProperty
      public String getProperty(String name)
Get the value of a logging property. The method returns null if the property is not found. Parameters: `name` - property name Returns: property value

### method:checkAccess() [NONE]
- #### checkAccess
      public void checkAccess()
                       throws SecurityException
Check that the current context is trusted to modify the logging configuration. This requires LoggingPermission("control"). If the check fails we throw a SecurityException, otherwise we return normally. Throws: `SecurityException` - if a security manager exists and if the caller does not have LoggingPermission("control").

### method:getLoggingMXBean() [NONE]
- #### getLoggingMXBean
      public static LoggingMXBean getLoggingMXBean()
  Returns `LoggingMXBean` for managing loggers. An alternative way to manage loggers is through the `PlatformLoggingMXBean` interface that can be obtained by calling:
           PlatformLoggingMXBean logging = ManagementFactory.getPlatformMXBean(PlatformLoggingMXBean.class);
Returns: a `LoggingMXBean` object. Since: 1.5 See Also: `PlatformLoggingMXBean`

### method:addConfigurationListener(java.lang.Runnable) [NONE]
- #### addConfigurationListener
      public LogManager addConfigurationListener(Runnable listener)
Adds a configuration listener to be invoked each time the logging configuration is read. If the listener is already registered the method does nothing. The listener is invoked with privileges that are restricted by the calling context of this method. The order in which the listeners are invoked is unspecified. It is recommended that listeners do not throw errors or exceptions. If a listener terminates with an uncaught error or exception then the first exception will be propagated to the caller of `readConfiguration()` (or `readConfiguration(java.io.InputStream)`) after all listeners have been invoked. Implementation Note: If more than one listener terminates with an uncaught error or exception, an implementation may record the additional errors or exceptions as suppressed exceptions . Parameters: `listener` - A configuration listener that will be invoked after the configuration changed. Returns: This LogManager. Throws: `SecurityException` - if a security manager exists and if the caller does not have LoggingPermission("control"). `NullPointerException` - if the listener is null. Since: 1.9

### method:removeConfigurationListener(java.lang.Runnable) [NONE]
- #### removeConfigurationListener
      public void removeConfigurationListener(Runnable listener)
Removes a previously registered configuration listener. Returns silently if the listener is not found. Parameters: `listener` - the configuration listener to remove. Throws: `NullPointerException` - if the listener is null. `SecurityException` - if a security manager exists and if the caller does not have LoggingPermission("control"). Since: 1.9